-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.triagedIssue has been triaged by sub teamIssue has been triaged by sub teamtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)
Description
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.
FMorschel
Metadata
Metadata
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.triagedIssue has been triaged by sub teamIssue has been triaged by sub teamtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)