-
Notifications
You must be signed in to change notification settings - Fork 218
package:test
should not depend on Dart SDK internals
#2210
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
Comments
CC @jakemac53 – I think (er, know) that @jakemac53 got this wired up before we had the "official" CLI. |
Yes, if we have a more official thing to use now we can swap to use that. |
FYI: we're now CRASHING w/ the latest dart dev SDK. |
mkustermann
added a commit
to mkustermann/test
that referenced
this issue
May 31, 2024
package:test should not depend and use Dart SDK internal files, flags or other internal things for invoking compilers. Instead it should use the public `dart compile wasm` command. Closes dart-lang#2210
Uploaded #2233 |
mkustermann
added a commit
that referenced
this issue
Jun 1, 2024
* Fix `dart run test -p chrome -c dart2wasm` package:test should not depend and use Dart SDK internal files, flags or other internal things for invoking compilers. Instead it should use the public `dart compile wasm` command. Closes #2210 * fix testing to do last supported and dev
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
package:test
seems to depend on an internal location and name of an AOT-compiled snapshot of e.g. dart2wasm compiler, see pkgs/test_core/lib/src/runner/wasm_compiler_pool.dart:3rd parties should not depend on
<dart-sdk>/lib/_internal/*
or<dart-sdk/bin/snapshots/*
.Why can
package:test
not usedart compile wasm
instead?/cc @kevmoo
The text was updated successfully, but these errors were encountered: