Update dependency dart to v3 #60
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate_dart-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
>=2.12.0 <3.0.0-><4.0.0Release Notes
dart-lang/sdk (dart)
v3.6.0Compare Source
Language
Dart 3.6 adds digit separators to the language. To use them, set your
package's [SDK constraint][language version] lower bound to 3.6 or greater
(
sdk: '^3.6.0').Digit separators
Digits in number literals (decimal integer literals, double literals,
scientific notation literals, and hexadecimal literals) can now include
underscores between digits, as "digit separators." The separators do not change
the value of a literal, but can serve to make the number more readable.
Separators are not allowed at the start of a number (this would be parsed as an
identifier), at the end of a number, or adjacent to another character in a
number, like
.,x, or theein scientific notation.to perform type inference on the operand of a
throwexpression has beenchanged from the "unknown type" to
Object. This makes the type system moreself-consistent, because it reflects the fact that it's not legal to throw
null. This change is not expected to make any difference in practice.Libraries
dart:ioBreaking Change #52444: Removed the
Platform()constructor, whichhas been deprecated since Dart 3.1.
Breaking Change #53618:
HttpClientnow responds to a redirectthat is missing a "Location" header by throwing
RedirectException, insteadof
StateError.dart:js_interopJSArrayBuffer,JSDataView, and concrete typed arraytypes e.g.
JSInt8Array.lengthand[]/[]=operators toJSArray.toJSCaptureThissothisis passed in from JavaScript to thecallback as the first parameter.
frommethod onJSArrayto create aJSArrayfrom a givenJavaScript iterable or array-like object.
Tools
CFE
DOWN algorithms in the CFE are changed to match the specification
and the corresponding implementations in the Analyzer. The upper and
lower closures of type schemas are now computed just before they are
passed into the subtype testing procedure instead of at the very
beginning of the UP and DOWN algorithms.
Dart format
this.orsuper..asandifclauses.Wasm compiler (dart2wasm)
dart.library.jsis now false on conditional imports indart2wasm. Note that it was already a static error to import
dart:jsdirectly (see #55266).
Pub
Support for workspaces. This allows you to develop and resolve multiple
packages from the same repo together. See https://dart.dev/go/pub-workspaces
for more info.
New command
dart pub bump. Increments the version number of the currentpackage.
For example:
dart pub bump minorwill change the version from1.2.3to1.3.0.New validation:
dart pub publishwill warn if yourgit statusis notclean.
New flag
dart pub upgrade --unlock-transitive.dart pub upgrade --unlock-transitive pkg, will unlock and upgrade all thedependencies of
pkginstead of justpkg.Analyzer
use_truncating_division][use_truncating_division] lint rule.omit_obvious_local_variable_types][omit_obvious_local_variable_types] lint rule.specify_nonobvious_local_variable_types][specify_nonobvious_local_variable_types] lint rule.avoid_futureor_void][avoid_futureor_void] lint rule."invert conditional expression".
v3.5.4Compare Source
v3.5.3Compare Source
issue resulting in a missing tab bar when DevTools is embedded in
IntelliJ and Android Studio (issue#56607).
DevTools is opened instead of only the first time (issue#56607).
embedded in IntelliJ and Android Studio (issue#56607).
v3.5.2Compare Source
ZLibDecoderwould incorrectly attempt to decompress datapast the end of the zlib footer (issue #56481).
dartfromPATHcould result in some commands notworking as expected (issues #56080, #56306, #56499).
setContextRootsrequests orbeing provided incorrect context roots in multi-package workspaces (issue
#56475).
v3.5.1Compare Source
include:inanalysis_options.yamlfile in a nestedfolder in the workspace (issue#56464).
dart compile wasmwhen optimizations areenabled (issue #56423).
dart2wasmcompiler in unsound-O3/-O4modes where aimplicit setter for a field of generic type will store
nullinstead of thefield value (issue #56374).
dart2wasmcompiler that can trigger in certain situationswhen using partial instantiations of generic tear-offs (constructors or static
methods) in constant expressions (issue #56440).
also known is UP, is provided the missing implementation for
StructuralParameterTypeobjects. In some corner cases cases thelacking implementation resulted in a crash of the compiler (issue #56457).
v3.5.0Compare Source
Language
Breaking Change #55418: The context used by the compiler to perform
type inference on the operand of an
awaitexpression has been changed tomatch the behavior of the analyzer. This change is not expected to make any
difference in practice.
Breaking Change #55436: The context used by the compiler to perform
type inference on the right hand side of an "if-null" expression (
e1 ?? e2)has been changed to match the behavior of the analyzer. change is expected to
have low impact on real-world code. But in principle it could cause
compile-time errors or changes in runtime behavior by changing inferred
types. The old behavior can be restored by supplying explicit types.
Libraries
dart:coreDateTimeon the web platform now storesmicroseconds. The web implementation is now practically compatible with the
native implementation, where it is possible to round-trip a timestamp in
microseconds through a
DateTimevalue without rounding the lowerdigits. This change might be breaking for apps that rely in some way on the
.microsecondcomponent always being zero, for example, expecting only threefractional second digits in the
toString()representation. Smalldiscrepancies in arithmetic due to rounding of web integers may still occur
for extreme values, (1)
microsecondsSinceEpochoutside the safe range,corresponding to dates with a year outside of 1685..2255, and (2) arithmetic
(
add,subtract,difference) where theDurationargument or resultexceeds 570 years.
dart:ioBreaking Change #55786:
SecurityContextis nowfinal. This meansthat
SecurityContextcan no longer be subclassed.SecurityContextsubclasses were never able to interoperate with other parts of
dart:io.A
ConnectionTaskcan now be created using an existingFuture<Socket>.Fixes #55562.
dart:typed_dataBreaking Change #53785: The unmodifiable view classes for typed data
have been removed. These classes were deprecated in Dart 3.4.
To create an unmodifiable view of a typed-data object, use the
asUnmodifiableView()methods added in Dart 3.3.Added superinterface
TypedDataListto typed data lists, implementing bothListandTypedData. Allows abstracting over all such lists without losingaccess to either the
Listor theTypedDatamembers.A
ByteDatais still only aTypedData, not a list.dart:js_interopBreaking Change #55508:
importModulenow accepts aJSAnyinsteadof a
Stringto support other JS values as well, likeTrustedScriptURLs.Breaking Change #55267:
isTruthyandnotnow returnJSBooleaninstead of
boolto be consistent with the other operators.Breaking Change
ExternalDartReferenceno longer implementsObject.ExternalDartReferencenow accepts a type parameterTwith a bound ofObject?to capture the type of the Dart object that is externalized.ExternalDartReferenceToObject.toDartObjectnow returns aT.ExternalDartReferenceToObjectandObjectToExternalDartReferenceare nowextensions on
TandExternalDartReference<T>, respectively, whereT extends Object?. See #55342 and #55536 for more details.Fixed some consistency issues with
Function.toJSacross all compilers.Specifically, calling
Function.toJSon the same function gives you a new JSfunction (see issue #55515), the maximum number of arguments that are
passed to the JS function is determined by the static type of the Dart
function, and extra arguments are dropped when passed to the JS function in
all compilers (see #48186).
Tools
Analyzer
unintended_html_in_doc_comment][unintended_html_in_doc_comment] lint rule.invalid_runtime_check_with_js_interop_types][invalid_runtime_check_with_js_interop_types] lint rule.document_ignores][document_ignores] lint rule.the switch becomes exhaustive.
constkeywords to child nodes, whereappropriate.
Pub
dart pub downgrade --tightento restrict lower bounds ofdependencies' constraints to the minimum that can be resolved.
Dart Runtime
The Dart VM only executes sound null safe code, running of unsound null
safe code using the option
--no-sound-null-safetyhas been removed.Dart_NewListOfandDart_IsLegacyTypefunctions areremoved from Dart C API.
Dart_DefaultCanonicalizeUrlis removed from the Dart C API.v3.4.4Compare Source
This is a patch release that:
Fixes an issue where pub would crash when failing to fetch advisories from
the server. (issue pub#4269).
Fixes an issue where
const bool.fromEnvironment('dart.library.ffi')is trueand conditional import condition
dart.library.ffiis true in dart2wasm.(issue #55948).
Fixes an issue where FFI calls with variadic arguments on MacOS Arm64
would mangle the arguments. (issue #55943).
v3.4.3Compare Source
This is a patch release that:
Fixes an issue where
DART_VM_OPTIONSwere not correctly parsed forstandalone Dart executables created with
dart compile exe(issue#55818).
Fixes a bug in dart2wasm that can result in a runtime error that says
array.new_fixed()has a constant larger than 10000 (issue #55873).Adds support for
--enable-experimentflag todart compilewasm(issue #55894).
Fixes an issue in dart2wasm compiler that can result in incorrect
nullability of type parameter (see #55895).
Disallows
dart:ffiimports in user code in dart2wasm (e.g. issuev3.4.2Compare Source
This is a patch release that:
Marks
dart compile wasmas no longer experimental.Fixes two bugs in exception handling in
asyncfunctions in dart2wasm(issues #55347, #55457).
Fixes restoration of
thisvariable insync*andasyncfunctions indart2wasm.
Implements missing control flow constructs (exceptions, switch/case with
yields) in
sync*in dart2wasm (issues #51342, #51343).Fixes a bug dart2wasm compiler that surfaces as a compiler crash when indexing
lists where the compiler proofs the list to be constant and the index is
out-of-bounds (issue #55817).
v3.4.1Compare Source
This is a patch release that:
Fixes a bug in the CFE which could manifest as compilation errors of Flutter
web apps when compiled with dart2wasm (issue #55714).
Fixes a bug in the pub client, such that
dart runwill not interfere withFlutter l10n (at least for most cases) (issue #55758).
v3.4.0Compare Source
Language
Dart 3.4 makes improvements to the type analysis of conditional expressions
(
e1 ? e2 : e3), if-null expressions (e1 ?? e2), if-null assignments(
e1 ??= e2), and switch expressions (switch (e) { p1 => e1, ... }). To takeadvantage of these improvements, set your package's
SDK constraint lower bound to 3.4 or greater
(
sdk: '^3.4.0').Breaking Change #54640: The pattern context type schema for
cast patterns has been changed from
Object?to_(the unknowntype), to align with the specification. This change is not expected
to make any difference in practice.
Breaking Change #54828: The type schema used by the compiler front end
to perform type inference on the operand of a null-aware spread operator
(
...?) in map and set literals has been made nullable, to match whatcurrently happens in list literals. This makes the compiler front end behavior
consistent with that of the analyzer. This change is expected to be very low
impact.
Libraries
dart:asyncParallelWaitErrorto get some meta-information thatit can expose in its
toString, and theIterable<Future>.waitand(Future,...,Future).waitextension methods now provide that information.Should make a
ParallelWaitErroreasier to log.dart:cliwaitForis removed in 3.4.dart:ffiStruct.createandUnion.createto create struct and union viewsof the sequence of bytes stored in a subtype of
TypedData.dart:ioBreaking change #53863:
Stdouthas a new fieldlineTerminator,which allows developers to control the line ending used by
stdoutandstderr. Classes thatimplement Stdoutmust define thelineTerminatorfield. The default semantics of
stdoutandstderrare not changed.Deprecates
FileSystemDeleteEvent.isDirectory, which always returnsfalse.dart:js_interopFixes an issue with several comparison operators in
JSAnyOperatorExtensionthat were declared to return
JSBooleanbut really returnedbool. This ledto runtime errors when trying to use the return values. The implementation now
returns a
JSBooleanto align with the interface. See issue #55024 formore details.
Added
ExternalDartReferenceand related conversion functionstoExternalReferenceandtoDartObject. This is a faster alternative toJSBoxedDartObject, but with fewer safety guarantees and fewerinteroperability capabilities. See #55187 for more details.
On dart2wasm,
JSBoxedDartObjectnow is an actual JS object that wraps theopaque Dart value instead of only externalizing the value. Like the JS
backends, you'll now get a more useful error when trying to use it in another
Dart runtime.
Added
isAhelper to make type checks easier with interop types. See#54138 for more details.
dart:typed_dataBREAKING CHANGE #53218 #53785: The unmodifiable view classes for
typed data are deprecated.
To create an unmodifiable view of a typed-data object, use the
asUnmodifiableView()methods added in Dart 3.3:The reason for this change is to allow more flexibility in the implementation
of typed data, so the native and web platforms can use different strategies
to ensure that typed data has good performance.
The deprecated types will be removed in Dart 3.5.
Tools
Analyzer
Improved code completion. Fixed over 50% of completion correctness bugs,
tagged
analyzer-completion-correctnessin the issuetracker.
Support for new annotations introduced in version 1.14.0 of the meta
package.
Support for the [
@doNotSubmit][@doNotSubmit] annotation, noting that any usage of anannotated member should not be submitted to source control.
Support for the [
@mustBeConst][@mustBeConst] annotation, which indicates that anannotated parameter only accepts constant arguments.
Linter
unnecessary_library_name][unnecessary_library_name] lint.missing_code_block_language_in_doc_comment][missing_code_block_language_in_doc_comment] lint.Compilers
value
""for alldart.library.foostrings, wheredart:foois not anavailable library. Instead there will only be entries for the available
libraries, like
dart.library.core, where the value was, and still is,"true". This should have no effect onconst bool.fromEnvironment(...)orconst String.fromEnvironment(...)without adefaultValueargument, anargument which was always ignored previously. It changes the behavior of
const bool.hasEnvironment(...)on such an input, away from always beingtrueand therefore useless.DevTools
To learn more, check out the release notes for versions
2.32.0 and 2.33.0.
Pub
Dependency resolution and
dart pub outdatedwill now surface if a dependencyis affected by a security advisory, unless the advisory is listed under a
ignored_advisoriessection in thepubspec.yamlfile. To learn more aboutpub's support for security advisories, visit
dart.dev/go/pub-security-advisories.
path-dependencies insidegit-dependencies are now resolved relative to thegit repo.
All
dart pubcommands can now be run from any subdirectory of a project. Pubwill find the first parent directory with a
pubspec.yamland operaterelative it.
New command
dart pub unpackthat downloads a package from pub.dev andextracts it to a subfolder of the current directory.
This can be useful for inspecting the code, or playing with examples.
Dart Runtime
Dart VM flags and options can now be provided to any executable generated
using
dart compile exevia theDART_VM_OPTIONSenvironment variable.DART_VM_OPTIONSshould be set to a list of comma-separated flags and optionswith no whitespace. Options that allow for multiple values to be provided as
comma-separated values are not supported (e.g.,
--timeline-streams=Dart,GC,Compiler).Example of a valid
DART_VM_OPTIONSenvironment variable:Dart VM no longer supports external strings:
Dart_IsExternalString,Dart_NewExternalLatin1StringandDart_NewExternalUTF16Stringfunctions areremoved from Dart C API.
v3.3.4Compare Source
This is a patch release that:
the enclosing library's
@JSannotation were actually using the invocation'senclosing library's
@JSannotation. (issue #55430).v3.3.3Compare Source
This is a patch release that:
v3.3.2Compare Source
This is a patch release that:
of their context in the code restored from dill files, causing crashes in the
incremental compiler whenever it restored a typedef from dill such that the
typedef contained a generic function type on its right-hand side (issue
#55158).
resolved in initializers of extension types (issue #55194).
DateTime.timeZoneNameon Windows, which was checking whether current date is in the summer or
standard time rather than checking if the given moment is in the summer or
standard time (issue #55240).
v3.3.1Compare Source
This is a patch release that:
extension types would fail to compile without an
@JSannotation on thelibrary (issue #55057).
operand of an
awaitexpression, unless the extension type itself implementsFuture(issue #55095).v3.3.0Compare Source
Language
Dart 3.3 adds extension types to the language. To use them, set your
package's [SDK constraint][language version] lower bound to 3.3 or greater
(
sdk: '^3.3.0').Extension types
An extension type wraps an existing type with a different, static-only
interface. It works in a way which is in many ways similar to a class that
contains a single final instance variable holding the wrapped object, but
without the space and time overhead of an actual wrapper object.
Extension types are introduced by extension type declarations. Each
such declaration declares a new named type (not just a new name for the
same type). It declares a representation variable whose type is the
representation type. The effect of using an extension type is that the
representation (that is, the value of the representation variable) has
the members declared by the extension type rather than the members declared
by its "own" type (the representation type). Example:
The declaration
Metersis an extension type that has representation typeint. It introduces an implicit constructorMeters(int value);and agetter
int get value.mandm.valueis the very same object, butmhas type
Metersandm.valuehas typeint. The point is thatmhas the members of
Metersandm.valuehas the members ofint.Extension types are entirely static, they do not exist at run time. If
ois the value of an expression whose static type is an extension type
Ewith representation type
R, thenois just a normal object whoserun-time type is a subtype of
R, exactly like the value of an expressionof type
R. Also the run-time value ofEisR(for example,E == Ris true). In short: At run time, an extension type is erased to the
corresponding representation type.
A method call on an expression of an extension type is resolved at
compile-time, based on the static type of the receiver, similar to how
extension method calls work. There is no virtual or dynamic dispatch. This,
combined with no memory overhead, means that extension types are zero-cost
wrappers around their representation value.
While there is thus no performance cost to using extension types, there is
a safety cost. Since extension types are erased at compile time, run-time
type tests on values that are statically typed as an extension type will
check the type of the representation object instead, and if the type check
looks like it tests for an extension type, like
is Meters, it actuallychecks for the representation type, that is, it works exactly like
is intat run time. Moreover, as mentioned above, if an extension type is used as
a type argument to a generic class or function, the type variable will be
bound to the representation type at run time. For example:
Extension types are useful when you are willing to sacrifice some run-time
encapsulation in order to avoid the overhead of wrapping values in
instances of wrapper classes, but still want to provide a different
interface than the wrapped object. An example of that is interop, where you
may have data that are not Dart objects to begin with (for example, raw
JavaScript objects when using JavaScript interop), and you may have large
collections of objects where it's not efficient to allocate an extra object
for each element.
Other changes
Breaking Change #54056: The rules for private field promotion have
been changed so that an abstract getter is considered promotable if there are
no conflicting declarations. There are no conflicting declarations if
there are no non-final fields, external fields, concrete getters, or
noSuchMethodforwarding getters with the same name in the same library.This makes the implementation more consistent and allows
type promotion in a few rare scenarios where it wasn't previously allowed.
It is unlikely, but this change could cause a breakage by changing
an inferred type in a way that breaks later code. For example:
Affected code can be fixed by adding an explicit type annotation.
For example, in the above snippet,
var xcan be changed toint? x.It's also possible that some continuous integration configurations might fail
if they have been configured to treat warnings as errors, because the expanded
type promotion could lead to one of the following warnings:
unnecessary_non_null_assertionunnecessary_castinvalid_null_aware_operatorThese warnings can be addressed in the usual way, by removing the unnecessary
operation in the first two cases, or changing
?.to.in the third case.To learn more about other rules surrounding type promotion,
check out the guide on Fixing type promotion failures.
Libraries
dart:coreString.fromCharCodesnow allowstartandendto be after the end ofthe
Iterableargument, just likeskipandtakedoes on anIterable.dart:ffi@Nativecan now be used on fields.Native.addressOf.elementAtpointer arithmetic extension methods oncore
Pointertypes are now deprecated.Migrate to the new
-and+operators instead.@FfiNativeannotation has been removed.Usages should be updated to use the
@Nativeannotation.dart:js_interoplike
JSAnywere previously represented using a custom erasure of@staticInteroptypes that were compiler-specific. They are now representedas extension types where their representation types are compiler-specific.
This means that user-defined
@staticInteroptypes that implementedJSAnyor
JSObjectcan no longer do so and need to useJSObject.fromInteropObject. Going forward, it's recommended to use extensiontypes to define interop APIs. Those extension types can still implement JS
types.
JSArrayandJSPromiseare now generictypes whose type parameter is a subtype of
JSAny?. Conversions to and fromthese types are changed to account for the type parameters of the Dart or JS
type, respectively.
dart:js_interopextensionmembers are moved to different extensions on the same type or a supertype to
better organize the API surface. See
JSAnyUtilityExtensionandJSAnyOperatorExtensionfor the new extensions. This shouldn't make adifference unless the extension names were explicitly used.
importModuleto allow users to dynamically import modules using the JSimport()expression.dart:js_interop_unsafehashelper to makehasPropertycalls more concise.dart:typed_dataBREAKING CHANGE (https://github.com/dart-lang/sdk/issues/53218) The
unmodifiable view classes for typed data are deprecated. Instead of using the
constructors for these classes to create an unmodifiable view, e.g.
use the new
asUnmodifiableView()methods:The reason for this change is to allow more flexibility in the implementation
of typed data so the native and web platforms can use different strategies
for ensuring typed data has good performance.
The deprecated types will be removed in a future Dart version.
dart:nativewrappersbasesothat none of their subtypes can be implemented. Implementing subtypes can lead
to crashes when passing such native wrapper to a native call, as it will try
to unwrap a native field that doesn't exist.
Tools
Dart command line
dart createcommand now uses v3 ofpackage:lints,including multiple new recommended lints by default.
To learn more about the updated collection of lints,
check out the
package:lints3.0.0 changelog entry.DevTools
To learn more, check out the release notes for versions
2.29.0, 2.30.0,
and 2.31.0.
Wasm compiler (dart2wasm)
dart:js_util,package:js, anddart:jsare now disallowed from being imported when compiling with
dart2wasm. Preferusing
dart:js_interopanddart:js_interop_unsafe.Development JavaScript compiler (DDC)
Type arguments of
package:jsinterop types are now printed asanyinsteadof being omitted. This is simply a change to the textual representation of
package js types that have type arguments. These type arguments are still
completely ignored by the type system at runtime.
Removed "implements <...>" text from the Chrome custom formatter display for
Dart classes. This information provides little value and keeping it imposes an
unnecessary maintenance cost.
Production JavaScript compiler (dart2js)
The
Invocationthat is passed tonoSuchMethodwill no longer have aminified
memberName, even when dart2js is invoked with--minify.See #54201 for more details.
Analyzer
pubspec.yamlfiles byadding an
# ignore: <diagnostic_id>comment.dart doccomment directives are now reported.flutter_style_todos][flutter_style_todos] lint now has a quick fix.Linter
iterable_contains_unrelated_typeandlist_remove_unrelated_typelints.Consider migrating to the expanded
[
collection_methods_unrelated_type][collection_methods_unrelated_type] lint.always_require_non_null_named_parametersavoid_returning_null,avoid_returning_null_for_futurev3.2.6Compare Source
v3.2.5Compare Source
v3.2.4Compare Source
v3.2.3Compare Source
This is a patch release that:
(issue #54232).
environments that don't support the integer division
instructions or x86-64 environments that don't support
SSE4.1 (issue #54215).
v3.2.2Compare Source
This is a patch release that:
Adjusts the nullablity computations in the implementation of the
upper bound algorithm in the compiler frontend (issue #53999).
Fixes missing closure code completion entries for function parameters
for LSP-based editors like VS Code (issue #54112).
v3.2.1Compare Source
This is a patch release that:
Fixes the left/mobile sidebar being empty on non-class pages
in documentation generated with
dart doc(issue #54073).Fixes a JSON array parsing bug that causes a segmentation fault when
flutter testis invoked with the--coverageflag(SDK issue #54059, Flutter issue #124145).
Upgrades Dart DevTools to version 2.28.3 (issue #54085).
v3.2.0Compare Source
Language
Dart 3.2 adds the following features. To use them, set your package's SDK
constraint lower bound to 3.2 or greater (
sdk: '^3.2.0').Private field promotion: In most circumstances, the types of private final
fields can now be promoted by null checks and
istests. For example:To ensure soundness, a field is not eligible for field promotion in the
following circumstances:
test and the usage, invalidating the promotion).
non-final field (because an access to an overridden field might resolve at
runtime to the overriding getter or field).
elsewhere in the program).
other unrelated class in the library (because a class elsewhere in the
program might extend one of the classes and implement the other, creating an
override relationship between them).
Cin the library whose interface contains agetter with the same name, but
Cdoes not have an implementation of thatgetter (such unimplemented getters aren't safe for field promotion, because
they are implicitly forwarded to
noSuchMethod, which might not return thesame value each time it's called).
Breaking Change #53167: Use a more precise split point for refutable
patterns. Previously, in an if-case statement, if flow analysis could prove
that the scrutinee expression was guaranteed to throw an exception, it would
sometimes fail to propagate type promotions implied by the pattern to the
(dead) code that follows. This change makes the type promotion behavior of
if-case statements consistent regardless of whether the scrutinee expression
throws an exception.
No live code is affected by this change, but there is a small chance that the
change in types will cause a compile-time error to appear in some dead code in
the user's project, where no compile-time error appeared previously.
Libraries
dart:asyncbroadcastparameter toStream.emptyconstructor.dart:cliwaitForis disabled by default and slated for removal in 3.4. Attemptingto call this function will now throw an exception. Users that still depend
on
waitForcan enable it by passing--enable_deprecated_wait_forflagto the VM.
dart:convertutf8.encode()andUtf8Codec.encode()fromList<int>toUint8List.dart:developerService.getIsolateIDmethod.getIsolateIdmethod toService.getObjectIdmethod toService.dart:ffiNativeCallable.isolateLocalconstructor. This createsNativeCallables with the same functionality asPointer.fromFunction,except that
NativeCallableaccepts closures.NativeCallable.keepIsolateAlivemethod, which determines whetherthe
NativeCallablekeeps the isolate that created it alive.NativeCallableconstructors can now accept closures. PreviouslyNativeCallables had the same restrictions asPointer.fromFunction, andcould only create callbacks for static functions.
NativeCallable.nativeFunctionnow throws anerror if is called after the
NativeCallablehas already beenclosed. Callsto
closeafter the first are now ignored.dart:ioBreaking change #53005: The headers returned by
HttpClientResponse.headersandHttpRequest.headersno longer includetrailing whitespace in their values.
Breaking change #53227: Folded headers values returned by
HttpClientResponse.headersandHttpRequest.headersnow have a spaceinserted at the fold point.
dart:isolateIsolate.packageConfigSyncandIsolate.resolvePackageUriSyncAPIs.dart:js_interopJSNumber.toDartis removed in favor oftoDartDoubleandtoDartInttomake the type explicit.
Object.toJSis also removed in favor ofObject.toJSBox. Previously, this function would allow Dart objects to flowinto JS unwrapped on the JS backends. Now, there's an explicit wrapper that is
added and unwrapped via
JSBoxedDartObject.toDart. Similarly,JSExportedDartObjectis renamed toJSBoxedDartObjectand the extensionsObjectToJSExportedDartObjectandJSExportedDartObjectToObjectare renamedto
ObjectToJSBoxedDartObjectandJSBoxedDartObjectToObjectin order toavoid confusion with
@JSExport.Type parameters must now be bound to a static interop type or one of the
dart:js_interoptypes likeJSNumberwhen used in an external API. Thisonly affects
dart:js_interopclasses and notpackage:jsor other forms ofJS interop.
dart:js_interoptypes:@staticInteroptypes can subtype onlyJSObjectandJSAnyfrom the set ofJS types in
dart:js_interop. Subtyping other types fromdart:js_interopwould result in confusing type errors before, so this makes it a static error.
dart:js_interopand@staticInteropAPIs:Static interop APIs will now use the same global context as non-static interop
instead of
globalThisto avoid a greater migration. Static interop APIs,either through
dart:js_interopor the@staticInteropannotation, have usedJavaScript's
globalThisas the global context. This is relevant to thingslike external top-level members or external constructors, as this is the root
context we expect those members to reside in. Historically, this was not the
case in dart2js and DDC. We used either
selfor DDC'sglobalin non-staticinterop APIs with
package:js. So, static interop APIs will now use one ofthose global contexts. Functionally, this should matter in only a very small
number of cases, like when using older browser versions.
dart:js_interop'sglobalJSObjectis also renamed toglobalContextand returns the globalcontext used in the lowerings.
dart:js_interopExternal APIs:External JS interop APIs when using
dart:js_interopare restricted to a setof allowed types. Namely, this includes the primitive types like
String, JStypes from
dart:js_interop, and other static interop types (either through@staticInteropor extension types).dart:js_interopisNullandisUndefined:nullandundefinedcan only be discerned in the JS backends. dart2wasmconflates the two values and treats them both as Dart null. Therefore, these
two helper methods should not be used on dart2wasm and will throw to avoid
potentially erroneous code.
dart:js_interoptypeofEqualsandinstanceof:Both APIs now return a
boolinstead of aJSBoolean.typeofEqualsalsonow takes in a
Stringinstead of aJSString.dart:js_interopJSAnyandJSObject:These types can only be implemented, and no longer extended, by user
@staticInteroptypes.dart:js_interopJSArray.withLength:This API now takes in an
intinstead ofJSNumber.Tools
Development JavaScript compiler (DDC)
JavaScript Object prototype.
JavaScript
Symbols andBigInts are now associated with their owninterceptor and should not be used with
package:jsclasses. These types werebeing intercepted with the assumption that they are a subtype of JavaScript's
Object, but this is incorrect. This lead to erroneous behavior when usingthese types as Dart
Objects. See #53106 for more details. Usedart:js_interop'sJSSymbolandJSBigIntwith extension types to interopwith these types.
Production JavaScript compiler (dart2js)
JavaScript
Symbols andBigInts are now associated with their owninterceptor and should not be used with
package:jsclasses. These types werebeing intercepted with the assumption that they are a subtype of JavaScript's
Object, but this is incorrect. This lead to erroneous behavior when usingthese types as Dart
Objects. See #53106 for more details. Usedart:js_interop'sJSSymbolandJSBigIntwith extension types to interopwith these types.
Dart command line
dart createcommand has a newclitemplateto quickly create Dart command-line applications
with basic argument parsing capabilities.
To learn more about using the template,
run
dart help create.Dart format
--enable-experimentcommand-line option to enable languageexperiments.
DevTools
2.28.1 releases of DevTools.
Linter
annotate_redeclares][annotate_redeclares] lint.use_build_context_synchronously][use_build_context_synchronously] lint as stable.Pub
dart pub upgrade --tightenwhich will update dependencies' lowerbounds in
pubspec.yamlto match the current version.dart pub get/add/upgradewill now show if a dependencychanged between direct, dev and transitive dependency.
dart pub upgradeno longer shows unchanged dependencies.v3.1.5Compare Source
This is a patch release that:
change in Node.js 21 affected the Dart Web compiler runtime. This patch
release accommodates for those changes (issue #53810).
v3.1.4Compare Source
This is a patch release that:
value of variables while debugging code (issue [#53747]).
v3.1.3Compare Source
This is a patch release that:
Fixes a bug in dart2js which would cause the compiler to crash when using
@staticInterop@anonymousfactory constructors with type parameters (seeissue #53579 for more details).
The standalone Dart VM now exports symbols only for the Dart_* embedding API
functions, avoiding conflicts with other DSOs loaded into the same process,
such as shared libraries loaded through
dart:ffi, that may have differentversions of the same symbols (issue [#53503]).
Fixes an issue with super slow access to variables while debugging.
The fix avoids searching static functions in the imported libraries
as references to members are fully resolved by the front-end. (issue
#53541)
v3.1.2Compare Source
This is a patch release that:
Fixes a bug in dart2js which crashed the compiler when a typed record pattern
was used outside the scope of a function body, such as in a field initializer.
For example
final x = { for (var (int a,) in someList) a: a };(issue #53449)
Fixes an expedient issue of users seeing an unhandled
exception pause in the debugger, please see
https://github.com/dart-lang/sdk/issues/53450 for more
details.
The fix uses try/catch in lookupAddresses instead of
Future error so that we don't see an unhandled exception
pause in the debugger (issue #53450)
v3.1.1Compare Source
This is a patch release that:
nested record pattern, where the nested record pattern uses record
destructuring shorthand syntax, for example
final ((:a, :b), c) = record;(issue #53352).
v3.1.0Compare Source
Libraries
dart:asyncinterfacemodifier to purely abstract classes:MultiStreamController,StreamConsumer,StreamIteratorandStreamTransformer. As a result, these types can only be implemented,not extended or mixed in.
dart:coreUri.baseon native platforms now respectsIOOverridesoverridingcurrent directory (#39796).
dart:ffiNativeCallableclass, which can be used to create callbacks thatallow native code to call into Dart code from any thread. See
NativeCallable.listener. In future releases,NativeCallablewill beupdated with more functionality, and will become the recommended way of
creating native callbacks for all use cases, replacing
Pointer.fromFunction.dart:iosameSiteto theCookieclass.SameSite.FileSystemEventissealed. This meansthat
FileSystemEventcannot be extended or implemented.Platformis instantiated.Platform.lineTerminatorwhich exposes the character or charactersthat the operating system uses to separate lines of text, e.g.,
"\r\n"on Windows.dart:js_interopObjectLiteralis removed fromdart:js_interop. It's no longer needed inorder to declare an object literal constructor with inline classes. As long as
an external constructor has at least one named parameter, it'll be treated as
an object literal constructor. If you want to create an object literal with no
named members, use
{}.jsify().Other libraries
package:js@staticInteropandexternalextension members:external@staticInteropmembers andexternalextension members can nolonger be used as tear-offs. Declare a closure or a non-
externalmethod thatcalls these members, and use that instead.
@staticInteropandexternalextension members:external@staticInteropmembers andexternalextension members willgenerate slightly different JS code for methods that have optional parameters.
Whereas before, the JS code passed in the default value for missing optionals,
it will now pass in only the provided members. This aligns with how JS
parameters work, where omitted parameters are actually omitted. For example,
calling
external void foo([int a, int b])asfoo(0)will now result infoo(0), and notfoo(0, null).Tools
DevTools
releases of DevTools.
Linter
your package's
analysis_options.yamlfile:no_self_assignmentsno_wildcard_variable_usesv3.0.7Compare Source
This is a patch release that:
bad codegen causing a
TypeErrororNoSuchMethodErrorto be thrownat runtime (issue #53001).
v3.0.6Compare Source
This is a patch release that:
assignments (issue #52767).
isorasexpressions involving record types with named fields (issue #52869).v3.0.5Compare Source
This is a patch release that:
ListFactorySpecializerduring Flutter web builds (issue #52403).v3.0.4Compare Source
This is a patch release that:
dart formatnow handles formatting nullable record typeswith no fields (dart_style issue #1224).
(issue #52480).
v3.0.3Compare Source
This is a patch release that:
returning an unboxed record (issue #52449).
or-pattern might be erroneously reported as being mismatched (issue #52373).
interfacemodifiers on the purely abstract classesMultiStreamController,StreamConsumer,StreamIteratorandStreamTransformer(issue #52334).InternetAddress.tryParseisused (issue #52423).
a pattern match using a variable or wildcard pattern with a nullable
record type (issue #52439).
cache on Windows (issue #52386).
v3.0.2Compare Source
This is a patch release that:
the fields don't match the cases (issue #52438).
generated with
dart doc(issue #3392).leading to higher memory usage (issue #52352).
(issue: #52078).
v3.0.1Compare Source
This is a patch release that:
(issue #124369).
and records (issue #51899).
voidin a switch case expression(issue #52191).
refers to a private getter (issue #52041).
whenandasas variable names in patterns(issue #52260).
(issue #52241).
v3.0.0Compare Source
Language
Dart 3.0 adds the following features. To use them, set your package's SDK
constraint lower bound to 3.0 or greater (
sdk: '^3.0.0').Records: Records are anonymous immutable data structures that let you
aggregate multiple values together, similar to tuples in other languages.
With records, you can return multiple values from a function, create composite
map keys, or use them any other place where you want to bundle a couple of
objects together.
For example, using a record to return two values:
Pattern matching: Expressions build values out of smaller pieces.
Conversely, patterns are an expressive tool for decomposing values back into
their constituent parts. Patterns can call getters on an object, access
elements from a list, pull fields out of a record, etc. For example, we can
destructure the record from the previous example like so:
Patterns can also be used in switch cases. There, you can destructure values
and also test them to see if they have a certain type or value:
Also, as you can see, non-empty switch cases no longer need
break;statements.
Breaking change: Dart 3.0 interprets switch cases as patterns instead of
constant expressions. Most constant expressions found in switch cases are
valid patterns with the same meaning (named constants, literals, etc.). You
may need to tweak a few constant expressions to make them valid. This only
affects libraries that have upgraded to language version 3.0.
Switch expressions: Switch expressions allow you to use patterns and
multi-way branching in contexts where a statement isn't allowed:
If-case statements and elements: A new if construct that matches a value
against a pattern and executes the then or else branch depending on whether
the pattern matches:
There is also a corresponding if-case element that can be used in collection
literals.
Sealed classes: When you mark a type
sealed, the compiler ensures thatswitches on values of that type exhaustively cover every subtype. This
enables you to program in an algebraic datatype style with the
compile-time safety you expect:
In this last example, the compiler reports an error that the switch doesn't
cover the subclass
Dusty.Class modifiers: New modifiers
final,interface,base, andmixinon
classandmixindeclarations let you control how the type can be used.By default, Dart is flexible in that a single class declaration can be used as
an interface, a superclass, or even a mixin. This flexibility can make it
harder to evolve an API over time without breaking users. We mostly keep the
current flexible defaults, but these new modifiers give you finer-grained
control over how the type can be used.
Breaking change: Class declarations from libraries that have been upgraded
to Dart 3.0 can no longer be used as mixins by default. If you want the class
to be usable as both a class and a mixin, mark it
mixin class. If you want it to be used only as a mixin, make it amixindeclaration. If you haven't upgraded a class to Dart 3.0, you can still use it
as a mixin.
Breaking change #50902: Dart reports a compile-time error if a
continuestatement targets a label that is not a loop (for,doandwhilestatements) or aswitchmember. Fix this by changing thecontinueto target a valid labeled statement.
Breaking change language/#2357: Starting in language version 3.0,
Dart reports a compile-time error if a colon (
:) is used as theseparator before the default value of an optional named parameter.
Fix this by changing the colon (
:) to an equal sign (=).Libraries
General changes
mixinclasses in the platform librariescan no longer be mixed in, unless they are explicitly marked as
mixin class.The following existing classes have been made mixin classes:
IterableIterableMixin(now alias forIterable)IterableBase(now alias forIterable)ListMixinSetMixinMapMixinLinkedListEntryStringConversionSinkdart:coreAdded
bool.parseandbool.tryParsestatic methods.Added
DateTime.timestamp()constructor to get current time as UTC.The type of
RegExpMatch.patternis nowRegExp, not justPattern.Breaking change #49529:
Listconstructor, as it wasn't null safe.Use list literals (e.g.
[]for an empty list or<int>[]for an emptytyped list) or [
List.filled][List.filled].onErrorargument on [int.parse][int.parse], [double.parse][double.parse],and [
num.parse][num.parse]. Use the [tryParse][tryParse] method instead.proxy][proxy] and [Provisional][Provisional] annotations.The original
proxyannotation has no effect in Dart 2,and the
Provisionaltype and [provisional][provisional] constantwere only used internally during the Dart 2.0 development process.
Deprecated.expires][Deprecated.expires] getter.Use [
Deprecated.message][Deprecated.message] instead.CastError][CastError] error.Use [
TypeError][TypeError] instead.FallThroughError][FallThroughError] error. The kind offall-through previously throwing this error was made a compile-time
error in Dart 2.0.
NullThrownError][NullThrownError] error. This error is neverthrown from null safe code.
AbstractClassInstantiationError][AbstractClassInstantiationError] error. It was madea compile-time error to call the constructor of an abstract class in Dart 2.0.
CyclicInitializationError][CyclicInitializationError]. Cyclic dependencies areno longer detected at runtime in null safe code. Such code will fail in other
ways instead, possibly with a StackOverflowError.
NoSuchMethodError][NoSuchMethodError] default constructor.Use the [
NoSuchMethodError.withInvocation][NoSuchMethodError.withInvocation] named constructor instead.BidirectionalIterator][BidirectionalIterator] class.Existing bidirectional iterators can still work, they just don't have
a shared supertype locking them to a specific name for moving backwards.
Breaking change when migrating code to Dart 3.0:
Some changes to platform libraries only affect code when that code is migrated
to language version 3.0.
The
Functiontype can no longer be implemented, extended or mixed in.Since Dart 2.0 writing
implements Functionhas been allowedfor backwards compatibility, but it has not had any effect.
In Dart 3.0, the
Functiontype isfinaland cannot be subtyped,preventing code from mistakenly assuming it works.
The following declarations can only be implemented, not extended:
ComparableExceptionIteratorPatternMatchRegExpRegExpMatchStackTraceStringSinkNone of these declarations contained any implementation to inherit,
and are marked as
interfaceto signify that they are only intendedas interfaces.
The following declarations can no longer be implemented or extended:
MapEntryOutOfMemoryErrorStackOverflowErrorExpandoWeakReferenceFinalizerThe
MapEntryvalue class is restricted to enable later optimizations.The remaining classes are tightly coupled to the platform and not
intended to be subclassed or implemented.
dart:asyncAdded extension member
waiton iterables and 2-9 tuples of futures.Breaking change #49529:
DeferredLibrary][DeferredLibrary] class.Use the [
deferred as][deferred as] import syntax instead.dart:collectionAdded extension members
nonNulls,firstOrNull,lastOrNull,singleOrNull,elementAtOrNullandindexedonIterables.Also exported from
dart:core.Deprecated the
HasNextIteratorclass (#50883).Breaking change when migrating code to Dart 3.0:
Some changes to platform libraries only affect code when it is migrated
to language version 3.0.
QueueLinkedListLinkedListEntryor extended:
HasNextIterator(Also deprecated.)HashMapLinkedHashMapHashSetLinkedHashSetDoubleLinkedQueueListQueueSplayTreeMapSplayTreeSetdart:developerBreaking change #49529:
MAX_USER_TAGS][MAX_USER_TAGS] constant.Use [
maxUserTags][maxUserTags] instead.Callbacks passed to
registerExtensionwill be run in the zone from whichthey are registered.
Breaking change #50231:
Metrics][Metrics], [Metric][Metric], [Counter][Counter],and [
Gauge][Gauge] classes as they have been broken since Dart 2.0.dart:ffi@FfiNativeannotation is now deprecated.Usages should be replaced with the new
@Nativeannotation.dart:htmlregisterElementand
registerElement2methods inDocumentandHtmlDocumenthave beenremoved. See #49536 for
details.
dart:mathSome changes to platform libraries only affect code when it is migrated
to language version 3.0.
Randominterface can only be implemented, not extended.dart:ionameandsignalNumberto theProcessSignalclass.NetworkInterface.listSupported. Has always returned true sinceDart 2.3.
httpEnableTimelineLoggingparameter name transition fromenableto
enabled. See #43638.#50868.
NetworkProfilingto accommodate newStringidsthat are introduced in vm_service:11.0.0
dart:js_utildeleteand thetypeoffunctionality.jsifyis now permissive and has inverse semantics todartify.jsifyanddartifyboth handle types they understand natively moreefficiently.
callMethodhas been aligned with the other methods andnow takes
Objectinstead ofString.Tools
Observatory
DevTools. Users requiring specific functionality in Observatory should set
the
--serve-observatoryflag.Web Dev Compiler (DDC)
-k,--kernel, and--dart-sdk.--nativeNonNullAsserts, which ensures web library APIsare sound in their nullability, is by default set to true in sound mode. For
more information on the flag, see NATIVE_NULL_ASSERTIONS.md.
dart2js
--native-null-assertions, which ensures web libraryAPIs are sound in their nullability, is by default set to true in sound mode,
unless
-O3or higher is passed, in which case they are not checked. For moreinformation on the flag, see NATIVE_NULL_ASSERTIONS.md.
Dart2js
the internal dart2js snapshot fails unless it is called from a supported
interface, such as
dart compile js,flutter build, orbuild_web_compilers. This is not expected to be a visible change.Formatter
sync*andasync*functions with=>bodies.<in collection literals.Analyzer
remaining hints are intended to be converted soon after the Dart 3.0 release.
This means that any (previously) hints reported by
dart analyzeare nowconsidered "fatal" (will result in a non-zero exit code). The previous
behavior, where such hints (now warnings) are not fatal, can be achieved by
using the
--no-fatal-warningsflag. This behavior can also be altered, on acode-by-code basis, by changing the severity of rules in an analysis
options file.
@Sinceannotation. When code in apackage uses a Dart SDK element annotated with
@Since, analyzer will reporta warning if the package's Dart SDK constraint allows versions of Dart
which don't include that element.
the number of plugins per analysis context to 1. (issue [#50981][]).
Linter
Updates the Linter to
1.35.0, which includes changes thatimplicit_reopenunnecessary_breakstype_literal_in_constant_patterninvalid_case_patternsenable_null_safetyinvariant_booleansprefer_bool_in_assertsprefer_equal_for_default_valuessuper_goes_lastunnecessary_parenthesisfalse-positives with null-aware expressions.void_checksto allow assignments ofFuture<dynamic>?to parameterstyped
FutureOr<void>?.use_build_context_synchronouslyin if conditions.avoid_private_typedef_functionswith generalizedtype aliases.
unnecessary_parenthesisto detect some doubled parens.void_checksto allow returningNeveras void.no_adjacent_strings_in_listto support set literals and for- andif-elements.
avoid_types_as_parameter_namesto handle type variables.avoid_positional_boolean_parametersto handle typedefs.avoid_redundant_argument_valuesto check parameters of redirectingconstructors.
prefer_const_literals_to_create_immutables.use_build_context_synchronouslyto check context properties.unnecessary_parenthesissupport for property accesses and methodinvocations.
unnecessary_parenthesisto allow parentheses in more null-awarecascade contexts.
unreachable_from_mainto track static elements.unnecessary_null_checksto not report on arguments passed toFuture.valueorCompleter.complete.always_use_package_importsandprefer_relative_importsasincompatible rules.
only_throw_errorsto not report onNever-typed expressions.unnecessary_lambdasto not report withlate finalvariables.avoid_function_literals_in_foreach_callsto not report with nullable-typed targets.
deprecated_member_use_from_same_packagewhich replaces thesoft-deprecated analyzer hint of the same name.
public_member_api_docsto not require docs on enum constructors.prefer_void_to_nullto not report on as-expressions.Migration tool removal
The null safety migration tool (
dart migrate) has been removed. If you stillhave code which needs to be migrated to null safety, please run
dart migrateusing Dart version 2.19, before upgrading to Dart version 3.0.
Pub
To preserve compatibility with null-safe code pre Dart 3, Pub will interpret a
language constraint indicating a language version of
2.12or higher and anupper bound of
<3.0.0as<4.0.0.For example
>=2.19.2 <3.0.0will be interpreted as>=2.19.2 <4.0.0.dart pub publishwill no longer warn aboutdependency_overrides. Dependencyoverrides only take effect in the root package of a resolution.
dart pub token addnow verifies that the given token is valid for includingin a header according to RFC 6750 section
2.1. This means they must
contain only the characters:
^[a-zA-Z0-9._~+/=-]+$. Before a failure wouldhappen when attempting to send the authorization header.
dart pub getand related commands will now by default also update thedependencies in the
examplefolder (if it exists). Use--no-exampletoavoid this.
On Windows the
PUB_CACHEhas moved to%LOCALAPPDATA%, since Dart 2.8 thePUB_CACHEhas been created in%LOCALAPPDATA%when one wasn't present.Hence, this only affects users with a
PUB_CACHEcreated by Dart 2.7 orearlier. If you have
path/to/.pub-cache/bininPATHyou may need toupdate your
PATH.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: pubspec.lock