Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VM still supports .packages files #60214

Open
lrhn opened this issue Feb 26, 2025 · 0 comments
Open

VM still supports .packages files #60214

lrhn opened this issue Feb 26, 2025 · 0 comments
Labels
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)

Comments

@lrhn
Copy link
Member

lrhn commented Feb 26, 2025

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.

@lrhn 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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)
Projects
None yet
Development

No branches or pull requests

1 participant