[beta][dart2wasm] Add more interop libraries to dry-run Issue description: dart:js_util and package:js imports are not being reported properly in the dry run anymore. We're also missing a few web libraries in the checking. What is the fix: Introduce new enums and check explicitly for the imports instead of relying on the JS interop checks. Also don't visit package:js in the dry run analysis. Why cherry-pick: Improves analytics which are somewhat incorrect today. Risk: Near none. This is only run as part of analytics collection in Flutter and if the code is incorrect, it will only affect analytics. Issue link: https://github.com/flutter/flutter/issues/178894 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/474940 Bug: https://github.com/flutter/flutter/issues/178894 Change-Id: Ia67c046bcf70a4e90db4711cc205bfcac8bc02bb Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/475928 Reviewed-by: Nate Biggs <natebiggs@google.com> Commit-Queue: Srujan Gaddam <srujzs@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.