Update dependency dart to v3 #205

renovate · 2023-08-22T18:28:25Z

This PR contains the following updates:

Package	Update	Change
dart (source)	major	`>=2.1.0 <3.0.0` -> `<4.0.0`

Release Notes

dart-lang/sdk (dart)

`v3.5.4`

Compare Source

`v3.5.3`

Compare Source

Fixes an issue with the DevTools Memory tool causing OOMs. and an
issue resulting in a missing tab bar when DevTools is embedded in
IntelliJ and Android Studio (issue#56607).
Fixes an issue with the DevTools release notes showing each time
DevTools is opened instead of only the first time (issue#56607).
Fixes an issue resulting in a missing tab bar when DevTools is
embedded in IntelliJ and Android Studio (issue#56607).

`v3.5.2`

Compare Source

Fixes a bug where ZLibDecoder would incorrectly attempt to decompress data
past the end of the zlib footer (issue #56481).
Fixes issue where running dart from PATH could result in some commands not
working as expected (issues #56080, #56306, #56499).
Fixes analysis server plugins not receiving setContextRoots requests or
being provided incorrect context roots in multi-package workspaces (issue
#56475).

`v3.5.1`

Compare Source

Fixes resolving include: in analysis_options.yaml file in a nested
folder in the workspace (issue#56464).
Fixes source maps generated by dart compile wasm when optimizations are
enabled (issue #56423).
Fixes a bug in the dart2wasm compiler in unsound -O3 / -O4 modes where a
implicit setter for a field of generic type will store null instead of the
field value (issue #56374).
Fixes a bug in the dart2wasm compiler that can trigger in certain situations
when using partial instantiations of generic tear-offs (constructors or static
methods) in constant expressions (issue #56440).
The algorithm for computing the standard upper bound of two types,
also known is UP, is provided the missing implementation for
StructuralParameterType objects. In some corner cases cases the
lacking implementation resulted in a crash of the compiler (issue #56457).

`v3.5.0`

Compare Source

Language

Breaking Change #55418: The context used by the compiler to perform
type inference on the operand of an await expression has been changed to
match 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:core`

Breaking Change #44876: DateTime on the web platform now stores
microseconds. The web implementation is now practically compatible with the
native implementation, where it is possible to round-trip a timestamp in
microseconds through a DateTime value without rounding the lower
digits. This change might be breaking for apps that rely in some way on the
.microsecond component always being zero, for example, expecting only three
fractional second digits in the toString() representation. Small
discrepancies in arithmetic due to rounding of web integers may still occur
for extreme values, (1) microsecondsSinceEpoch outside the safe range,
corresponding to dates with a year outside of 1685..2255, and (2) arithmetic
(add, subtract, difference) where the Duration argument or result
exceeds 570 years.

`dart:io`

Breaking Change #55786: SecurityContext is now final. This means
that SecurityContext can no longer be subclassed. SecurityContext
subclasses were never able to interoperate with other parts of dart:io.
A ConnectionTask can now be created using an existing Future<Socket>.
Fixes #55562.

`dart:typed_data`

Breaking 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 TypedDataList to typed data lists, implementing both
List and TypedData. Allows abstracting over all such lists without losing
access to either the List or the TypedData members.
A ByteData is still only a TypedData, not a list.

`dart:js_interop`

Breaking Change #55508: importModule now accepts a JSAny instead
of a String to support other JS values as well, like TrustedScriptURLs.
Breaking Change #55267: isTruthy and not now return JSBoolean
instead of bool to be consistent with the other operators.
Breaking Change ExternalDartReference no longer implements Object.
ExternalDartReference now accepts a type parameter T with a bound of
Object? to capture the type of the Dart object that is externalized.
ExternalDartReferenceToObject.toDartObject now returns a T.
ExternalDartReferenceToObject and ObjectToExternalDartReference are now
extensions on T and ExternalDartReference<T>, respectively, where T extends Object?. See #55342 and #55536 for more details.
Fixed some consistency issues with Function.toJS across all compilers.
Specifically, calling Function.toJS on the same function gives you a new JS
function (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

Add the [unintended_html_in_doc_comment][unintended_html_in_doc_comment] lint rule.
Add the [invalid_runtime_check_with_js_interop_types][invalid_runtime_check_with_js_interop_types] lint rule.
Add the [document_ignores][document_ignores] lint rule.
Add quick fixes for more than 70 diagnostics.
The "Add missing switch cases" quick fix now adds multiple cases, such that
the switch becomes exhaustive.
The "Remove const" quick fix now adds const keywords to child nodes, where
appropriate.

Pub

New flag dart pub downgrade --tighten to restrict lower bounds of
dependencies' 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-safety has been removed.
Dart_NewListOf and Dart_IsLegacyType functions are
removed from Dart C API.
Dart_DefaultCanonicalizeUrl is removed from the Dart C API.

`v3.4.4`

Compare 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 true
and conditional import condition dart.library.ffi is 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.3`

Compare Source

This is a patch release that:

Fixes an issue where DART_VM_OPTIONS were not correctly parsed for
standalone 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-experiment flag to dart compile wasm
(issue #55894).
Fixes an issue in dart2wasm compiler that can result in incorrect
nullability of type parameter (see #55895).
Disallows dart:ffi imports in user code in dart2wasm (e.g. issue
[#53910]) as dart2wasm's currently only supports a small subset of
dart:ffi (issue #55890).

`v3.4.2`

Compare Source

This is a patch release that:

Marks dart compile wasm as no longer experimental.
Fixes two bugs in exception handling in async functions in dart2wasm
(issues #55347, #55457).
Fixes restoration of this variable in sync* and async functions in
dart2wasm.
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.1`

Compare 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 run will not interfere with
Flutter l10n (at least for most cases) (issue #55758).

`v3.4.0`

Compare 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 take
advantage 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 unknown
type), 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 what
currently 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:async`

Added option for ParallelWaitError to get some meta-information that
it can expose in its toString, and the Iterable<Future>.wait and
(Future,...,Future).wait extension methods now provide that information.
Should make a ParallelWaitError easier to log.

`dart:cli`

Breaking change [#52121][]: waitFor is removed in 3.4.

`dart:ffi`

Added Struct.create and Union.create to create struct and union views
of the sequence of bytes stored in a subtype of TypedData.

`dart:io`

Breaking change #53863: Stdout has a new field lineTerminator,
which allows developers to control the line ending used by stdout and
stderr. Classes that implement Stdout must define the lineTerminator
field. The default semantics of stdout and stderr are not changed.
Deprecates FileSystemDeleteEvent.isDirectory, which always returns
false.

`dart:js_interop`

Fixes an issue with several comparison operators in JSAnyOperatorExtension
that were declared to return JSBoolean but really returned bool. This led
to runtime errors when trying to use the return values. The implementation now
returns a JSBoolean to align with the interface. See issue #55024 for
more details.
Added ExternalDartReference and related conversion functions
toExternalReference and toDartObject. This is a faster alternative to
JSBoxedDartObject, but with fewer safety guarantees and fewer
interoperability capabilities. See #55187 for more details.
On dart2wasm, JSBoxedDartObject now is an actual JS object that wraps the
opaque 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 isA helper to make type checks easier with interop types. See
#54138 for more details.

`dart:typed_data`

BREAKING 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:
```
Uint8List data = ...;
final readOnlyView = data.asUnmodifiableView();
// readOnlyView has type Uint8List, and throws if attempted modified.
```
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-correctness in the issue
tracker.
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 an
  annotated member should not be submitted to source control.
- Support for the [@mustBeConst][@mustBeConst] annotation, which indicates that an
  annotated parameter only accepts constant arguments.

Linter

Added the [unnecessary_library_name][unnecessary_library_name] lint.
Added the [missing_code_block_language_in_doc_comment][missing_code_block_language_in_doc_comment] lint.

Compilers

The compilation environment will no longer pretend to contain entries with
value "" for all dart.library.foo strings, where dart:foo is not an
available 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 on const bool.fromEnvironment(...) or
const String.fromEnvironment(...) without a defaultValue argument, an
argument which was always ignored previously. It changes the behavior of
const bool.hasEnvironment(...) on such an input, away from always being
true and therefore useless.

DevTools

Updated DevTools to version 2.33.0 from 2.31.1.
To learn more, check out the release notes for versions
2.32.0 and 2.33.0.

Pub

Dependency resolution and dart pub outdated will now surface if a dependency
is affected by a security advisory, unless the advisory is listed under a
ignored_advisories section in the pubspec.yaml file. To learn more about
pub's support for security advisories, visit
dart.dev/go/pub-security-advisories.
path-dependencies inside git-dependencies are now resolved relative to the
git repo.
All dart pub commands can now be run from any subdirectory of a project. Pub
will find the first parent directory with a pubspec.yaml and operate
relative it.
New command dart pub unpack that downloads a package from pub.dev and
extracts 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 exe via the DART_VM_OPTIONS environment variable.
DART_VM_OPTIONS should be set to a list of comma-separated flags and options
with 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_OPTIONS environment variable:
```
DART_VM_OPTIONS=--random_seed=42,--verbose_gc
```
Dart VM no longer supports external strings: Dart_IsExternalString,
Dart_NewExternalLatin1String and Dart_NewExternalUTF16String functions are
removed from Dart C API.

`v3.3.4`

Compare Source

This is a patch release that:

Fixes an issue with JS interop in dart2wasm where JS interop methods that used
the enclosing library's @JS annotation were actually using the invocation's
enclosing library's @JS annotation. (issue #55430).

`v3.3.3`

Compare Source

This is a patch release that:

Fixes an issue where dart vm crashed when running on pre-SSE41 older CPUs on Windows (issue #55211).

`v3.3.2`

Compare Source

This is a patch release that:

Fixes an issue in the CFE that placed some structural parameter references out
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).
Fixes an issue in the CFE that prevented redirecting factories from being
resolved in initializers of extension types (issue #55194).
Fixes an issues with VM's implementation of DateTime.timeZoneName
on 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.1`

Compare Source

This is a patch release that:

Fixes an issue in dart2js where object literal constructors in interop
extension types would fail to compile without an @JS annotation on the
library (issue #55057).
Disallows certain types involving extension types from being used as the
operand of an await expression, unless the extension type itself implements
Future (issue #55095).

`v3.3.0`

Compare 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:

extension type Meters(int value) {
  String get label => '${value}m';
  Meters operator +(Meters other) => Meters(value + other.value);
}

void main() {
  var m = Meters(42); // Has type `Meters`.
  var m2 = m + m; // OK, type `Meters`.
  // int i = m; // Compile-time error, wrong type.
  // m.isEven; // Compile-time error, no such member.
  assert(identical(m, m.value)); // Succeeds.
}

The declaration Meters is an extension type that has representation type
int. It introduces an implicit constructor Meters(int value); and a
getter int get value. m and m.value is the very same object, but m
has type Meters and m.value has type int. The point is that m
has the members of Meters and m.value has the members of int.

Extension types are entirely static, they do not exist at run time. If o
is the value of an expression whose static type is an extension type E
with representation type R, then o is just a normal object whose
run-time type is a subtype of R, exactly like the value of an expression
of type R. Also the run-time value of E is R (for example, E == R
is 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 actually
checks for the representation type, that is, it works exactly like is int
at 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:

void main() {
  var meters = Meters(3);

  // At run time, `Meters` is just `int`.
  print(meters is int); // Prints "true".
  print(<Meters>[] is List<int>); // Prints "true".

  // An explicit cast is allowed and succeeds as well:
  List<Meters> meterList = <int>[1, 2, 3] as List<Meters>;
  print(meterList[1].label); // Prints "2m".
}

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
noSuchMethod forwarding 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:
```
class A {
  int? get _field;
}
class B extends A {
  final int? _field;
  B(this._field);
}
test(A a) {
  if (a._field != null) {
    var x = a._field; // Previously had type `int?`; now has type `int`
    ...
    x = null; // Previously allowed; now causes a compile-time error.
  }
}
```
Affected code can be fixed by adding an explicit type annotation.
For example, in the above snippet, var x can be changed to int? 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_assertion
- unnecessary_cast
- invalid_null_aware_operator
These 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:core`

String.fromCharCodes now allow start and end to be after the end of
the Iterable argument, just like skip and take does on an Iterable.

`dart:ffi`

In addition to functions, @Native can now be used on fields.
Allow taking the address of native functions and fields via
Native.addressOf.
The elementAt pointer arithmetic extension methods on
core Pointer types are now deprecated.
Migrate to the new - and + operators instead.
The experimental and deprecated @FfiNative annotation has been removed.
Usages should be updated to use the @Native annotation.

`dart:js_interop`

Breaking Change in the representation of JS types #52687: JS types
like JSAny were previously represented using a custom erasure of
@staticInterop types that were compiler-specific. They are now represented
as extension types where their representation types are compiler-specific.
This means that user-defined @staticInterop types that implemented JSAny
or JSObject can no longer do so and need to use
JSObject.fromInteropObject. Going forward, it's recommended to use extension
types to define interop APIs. Those extension types can still implement JS
types.
JSArray and JSPromise generics: JSArray and JSPromise are now generic
types whose type parameter is a subtype of JSAny?. Conversions to and from
these types are changed to account for the type parameters of the Dart or JS
type, respectively.
Breaking Change in names of extensions: Some dart:js_interop extension
members are moved to different extensions on the same type or a supertype to
better organize the API surface. See JSAnyUtilityExtension and
JSAnyOperatorExtension for the new extensions. This shouldn't make a
difference unless the extension names were explicitly used.
Add importModule to allow users to dynamically import modules using the JS
import() expression.

`dart:js_interop_unsafe`

Add has helper to make hasProperty calls more concise.

`dart:typed_data`

BREAKING 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.
```
Uint8List data = ...
final readOnlyView = UnmodifiableUint8ListView(data);
```
use the new asUnmodifiableView() methods:
```
Uint8List data = ...
final readOnlyView = data.asUnmodifiableView();
```
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:nativewrappers`

Breaking Change #51896: The NativeWrapperClasses are marked base so
that 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

The dart create command now uses v3 of package:lints,
including multiple new recommended lints by default.
To learn more about the updated collection of lints,
check out the package:lints 3.0.0 changelog entry.

DevTools

Updated DevTools to version 2.31.1 from 2.28.1.
To learn more, check out the release notes for versions
2.29.0, 2.30.0,
and 2.31.0.

Wasm compiler (dart2wasm)

Breaking Change #54004: dart:js_util, package:js, and dart:js
are now disallowed from being imported when compiling with dart2wasm. Prefer
using dart:js_interop and dart:js_interop_unsafe.

Development JavaScript compiler (DDC)

Type arguments of package:js interop types are now printed as any instead
of 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)

Breaking Change #54201:
The Invocation that is passed to noSuchMethod will no longer have a
minified memberName, even when dart2js is invoked with --minify.
See #54201 for more details.

Analyzer

You can now suppress diagnostics in pubspec.yaml files by
adding an # ignore: <diagnostic_id> comment.
Invalid dart doc comment directives are now reported.
The [flutter_style_todos][flutter_style_todos] lint now has a quick fix.

Linter

Removed the iterable_contains_unrelated_type and
list_remove_unrelated_type lints.
Consider migrating to the expanded
[collection_methods_unrelated_type][collection_methods_unrelated_type] lint.
Removed various lints that are no longer necessary with sound null safety:
- always_require_non_null_named_parameters
- avoid_returning_null,
- avoid_returning_null_for_future

This is a patch release that:

Disallows final fields to be used in a constant context during analysis
(issue #54232).
Upgrades Dart DevTools to version 2.28.4 (issue #54213).
Fixes new AOT snapshots in the SDK failing with SIGILL in ARM
environments that don't support the integer division
instructions or x86-64 environments that don't support
SSE4.1 (issue #54215).

`v3.2.2`

Compare 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.1`

Compare 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 test is invoked with the --coverage flag
(SDK issue #54059, Flutter issue #124145).
Upgrades Dart DevTools to version 2.28.3 (issue #54085).

`v3.2.0`

Compare 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 is tests. For example:
```
class Example {
  final int? _privateField;
  Example(this._privateField);

  f() {
    if (_privateField != null) {
      // _privateField has now been promoted; you can use it without
      // null checking it.
      int i = _privateField; // OK
    }
  }
}

// Private field promotions also work from outside of the class:
f(Example x) {
  if (x._privateField != null) {
    int i = x._privateField; // OK
  }
}
```
To ensure soundness, a field is not eligible for field promotion in the
following circumstances:
- If it's not final (because a non-final field could be changed in between the
  test and the usage, invalidating the promotion).
- If it's overridden elsewhere in the library by a concrete getter or a
  non-final field (because an access to an overridden field might resolve at
  runtime to the overriding getter or field).
- If it's not private (because a non-private field might be overridden
  elsewhere in the program).
- If it has the same name as a concrete getter or a non-final field in some
  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).
- If there is a concrete class C in the library whose interface contains a
  getter with the same name, but C does not have an implementation of that
  getter (such unimplemented getters aren't safe for field promotion, because
  they are implicitly forwarded to noSuchMethod, which might not return the
  same 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:async`

Added broadcast parameter to Stream.empty constructor.

`dart:cli`

Breaking change #52121:
- waitFor is disabled by default and slated for removal in 3.4. Attempting
  to call this function will now throw an exception. Users that still depend
  on waitFor can enable it by passing --enable_deprecated_wait_for flag
  to the VM.

`dart:convert`

Breaking change #52801:
- Changed return types of utf8.encode() and Utf8Codec.encode() from
  List<int> to Uint8List.

`dart:developer`

Deprecated the Service.getIsolateID method.
Added getIsolateId method to Service.
Added getObjectId method to Service.

`dart:ffi`

Added the NativeCallable.isolateLocal constructor. This creates
NativeCallables with the same functionality as Pointer.fromFunction,
except that NativeCallable accepts closures.
Added the NativeCallable.keepIsolateAlive method, which determines whether
the NativeCallable keeps the isolate that created it alive.
All NativeCallable constructors can now accept closures. Previously
NativeCallables had the same restrictions as Pointer.fromFunction, and
could only create callbacks for static functions.
Breaking change #53311: NativeCallable.nativeFunction now throws an
error if is called after the NativeCallable has already been closed. Calls
to close after the first are now ignored.

`dart:io`

Breaking change #53005: The headers returned by
HttpClientResponse.headers and HttpRequest.headers no longer include
trailing whitespace in their values.
Breaking change #53227: Folded headers values returned by
HttpClientResponse.headers and HttpRequest.headers now have a space
inserted at the fold point.

`dart:isolate`

Added Isolate.packageConfigSync and Isolate.resolvePackageUriSync APIs.

`dart:js_interop`

Breaking Change on JSNumber.toDart and Object.toJS:
JSNumber.toDart is removed in favor of toDartDouble and toDartInt to
make the type explicit. Object.toJS is also removed in favor of
Object.toJSBox. Previously, this function would allow Dart objects to flow
into JS unwrapped on the JS backends. Now, there's an explicit wrapper that is
added and unwrapped via JSBoxedDartObject.toDart. Similarly,
JSExportedDartObject is renamed to JSBoxedDartObject and the extensions
ObjectToJSExportedDartObject and JSExportedDartObjectToObject are renamed
to ObjectToJSBoxedDartObject and JSBoxedDartObjectToObject in order to
avoid confusion with @JSExport.
Type parameters in external APIs:
Type parameters must now be bound to a static interop type or one of the
dart:js_interop types like JSNumber when used in an external API. This
only affects dart:js_interop classes and not package:js or other forms of
JS interop.
Subtyping dart:js_interop types:
@staticInterop types can subtype only JSObject and JSAny from the set of
JS types in dart:js_interop. Subtyping other types from dart:js_interop
would result in confusing type errors before, so this makes it a static error.
Global context of dart:js_interop and @staticInterop APIs:
Static interop APIs will now use the same global context as non-static interop
instead of globalThis to avoid a greater migration. Static interop APIs,
either through dart:js_interop or the @staticInterop annotation, have used
JavaScript's globalThis as the global context. This is relevant to things
like 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 self or DDC's global in non-static
interop APIs with package:js. So, static interop APIs will now use one of
those global contexts. Functionally, this should matter in only a very small
number of cases, like when using older browser versions. dart:js_interop's
globalJSObject is also renamed to globalContext and returns the global
context used in the lowerings.
Breaking Change on Types of dart:js_interop External APIs:
External JS interop APIs when using dart:js_interop are restricted to a set
of allowed types. Namely, this includes the primitive types like String, JS
types from dart:js_interop, and other static interop types (either through
@staticInterop or extension types).
Breaking Change on dart:js_interop isNull and isUndefined:
null and undefined can only be discerned in the JS backends. dart2wasm
conflates 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.
Breaking Change on dart:js_interop typeofEquals and instanceof:
Both APIs now return a bool instead of a JSBoolean. typeofEquals also
now takes in a String instead of a JSString.
Breaking Change on dart:js_interop JSAny and JSObject:
These types can only be implemented, and no longer extended, by user
@staticInterop types.
Breaking Change on dart:js_interop JSArray.withLength:
This API now takes in an int instead of JSNumber.

Tools

Development JavaScript compiler (DDC)

Applications compiled by DDC will no longer add members to the native
JavaScript Object prototype.
Breaking change for JS interop with Symbols and BigInts:
JavaScript Symbols and BigInts are now associated with their own
interceptor and should not be used with package:js classes. These types were
being intercepted with the assumption that they are a subtype of JavaScript's
Object, but this is incorrect. This lead to erroneous behavior when using
these types as Dart Objects. See #53106 for more details. Use
dart:js_interop's JSSymbol and JSBigInt with extension types to interop
with these types.

Production JavaScript compiler (dart2js)

Breaking change for JS interop with Symbols and BigInts:
JavaScript Symbols and BigInts are now associated with their own
interceptor and should not be used with package:js classes. These types were
being intercepted with the assumption that they are a subtype of JavaScript's
Object, but this is incorrect. This lead to erroneous behavior when using
these types as Dart Objects. See #53106 for more details. Use
dart:js_interop's JSSymbol and JSBigInt with extension types to interop
with these types.

Dart command line

The dart create command has a new cli template
to quickly create Dart command-line applications
with basic argument parsing capabilities.
To learn more about using the template,
run dart help create.

Dart format

Always split enum declarations containing a line comment.
Fix regression in splitting type annotations with library prefixes.
Support --enable-experiment command-line option to enable language
experiments.

DevTools

Incorporated the 2.26.1, 2.27.0, and
2.28.1 releases of DevTools.

Linter

Added the experimental [annotate_redeclares][annotate_redeclares] lint.
Marked the [use_build_context_synchronously][use_build_context_synchronously] lint as stable.

Pub

New option dart pub upgrade --tighten which will update dependencies' lower
bounds in pubspec.yaml to match the current version.
The commands dart pub get/add/upgrade will now show if a dependency
changed between direct, dev and transitive dependency.
The command dart pub upgrade no longer shows unchanged dependencies.

`v3.1.5`

Compare Source

This is a patch release that:

Fixes an issue affecting Dart compiled to JavaScript running in Node.js 21. A
change in Node.js 21 affected the Dart Web compiler runtime. This patch
release accommodates for those changes (issue #53810).

`v3.1.4`

Compare Source

This is a patch release that:

Fixes an issue in the Dart VM, users are not being able to see
value of variables while debugging code (issue [#53747]).

`v3.1.3`

Compare Source

This is a patch release that:

Fixes a bug in dart2js which would cause the compiler to crash when using
@staticInterop @anonymous factory constructors with type parameters (see
issue #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 different
versions 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.2`

Compare 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 https://github.com/dart-lang/sdk/issues/53450es/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.1`

Compare Source

This is a patch release that:

Fixes a bug in the parser which prevented a record pattern from containing a
nested record pattern, where the nested record pattern uses record
destructuring shorthand syntax, for example final ((:a, :b), c) = record;
(issue #53352).

`v3.1.0`

Compare Source

Libraries

`dart:async`

Breaking change #52334:
- Added the interface modifier to purely abstract classes:
  MultiStreamController, StreamConsumer, StreamIterator and
  StreamTransformer. As a result, these types can only be implemented,
  not extended or mixed in.

`dart:core`

Uri.base on native platforms now respects IOOverrides overriding
current directory (#39796).

`dart:ffi`

Added the NativeCallable class, which can be used to create callbacks that
allow native code to call into Dart code from any thread. See
NativeCallable.listener. In future releases, NativeCallable will be
updated with more functionality, and will become the recommended way of
creating native callbacks for all use cases, replacing Pointer.fromFunction.

`dart:io`

Breaking change [#51486][]:
- Added sameSite to the Cookie class.
- Added class SameSite.
Breaking change [#52027][]: FileSystemEvent is
sealed. This means
that FileSystemEvent cannot be extended or implemented.
Added a deprecation warning when Platform is instantiated.

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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Update dependency dart to v3

aae7bec

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency dart to v3 #205

Update dependency dart to v3 #205

renovate bot commented Aug 22, 2023 •

edited

Loading

Update dependency dart to v3 #205

Are you sure you want to change the base?

Update dependency dart to v3 #205

Conversation

renovate bot commented Aug 22, 2023 • edited Loading

Release Notes

Language

Libraries

dart:core

dart:io

dart:typed_data

dart:js_interop

Tools

Analyzer

Pub

Dart Runtime

Language

Libraries

dart:async

dart:cli

dart:ffi

dart:io

dart:js_interop

dart:typed_data

Tools

Analyzer

Linter

Compilers

DevTools

Pub

Dart Runtime

Language

Extension types

Other changes

Libraries

dart:core

dart:ffi

dart:js_interop

dart:js_interop_unsafe

dart:typed_data

dart:nativewrappers

Tools

Dart command line

DevTools

Wasm compiler (dart2wasm)

Development JavaScript compiler (DDC)

Production JavaScript compiler (dart2js)

Analyzer

Linter

Language

Libraries

dart:async

dart:cli

dart:convert

dart:developer

dart:ffi

dart:io

dart:isolate

dart:js_interop

Tools

Development JavaScript compiler (DDC)

Production JavaScript compiler (dart2js)

Dart command line

Dart format

DevTools

Linter

Pub

Libraries

dart:async

dart:core

dart:ffi

dart:io

Configuration

renovate bot commented Aug 22, 2023 •

edited

Loading

`dart:core`

`dart:io`

`dart:typed_data`

`dart:js_interop`

`dart:async`

`dart:cli`

`dart:ffi`

`dart:io`

`dart:js_interop`

`dart:typed_data`

`dart:core`

`dart:ffi`

`dart:js_interop`

`dart:js_interop_unsafe`

`dart:typed_data`

`dart:nativewrappers`

`dart:async`

`dart:cli`

`dart:convert`

`dart:developer`

`dart:ffi`

`dart:io`

`dart:isolate`

`dart:js_interop`

`dart:async`

`dart:core`

`dart:ffi`

`dart:io`