You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The VM still supports package configuration using .packages files when spawning isolates.
The test tests/lib/isolate/scenarios/automatic_resolution_spec/package_resolve_test.dart tests this, using a .packages file in the same directory.
A .packages file is otherwise no longer supported. The language versioning feature was introduced in Dart 2.8, and while it still supported .packages at that point, any package configured through a .packages file would have a default language version of 2.7.
Since Dart 3.0, language version 2.7 is no longer supported, so any package configured by a .packages file must no longer compile.
The VM should just stop supporting .packages files. So should any other tool which is Dart 3.0 compatible.
The text was updated successfully, but these errors were encountered:
lrhn
added
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
labels
Feb 26, 2025
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
The VM still supports package configuration using
.packages
files when spawning isolates.The test
tests/lib/isolate/scenarios/automatic_resolution_spec/package_resolve_test.dart
tests this, using a.packages
file in the same directory.A
.packages
file is otherwise no longer supported. The language versioning feature was introduced in Dart 2.8, and while it still supported.packages
at that point, any package configured through a.packages
file would have a default language version of 2.7.Since Dart 3.0, language version 2.7 is no longer supported, so any package configured by a
.packages
file must no longer compile.The VM should just stop supporting
.packages
files. So should any other tool which is Dart 3.0 compatible.The text was updated successfully, but these errors were encountered: