[dart2wasm] Introduce "load ids" to dart2wasm deferred loading. Load ids provide a way to reduce the overhead of deferred loading. By default deferred loading requires mapping `loadLibrary` calls to a list of modules. This requires including (1) library uris, (2) prefix names and (3) module names directly in the main module. With this loading modules is easier as the loading function gets the exact filename. Load ids provide an alternative approach where the compiler emits a separate file mapping a load ID to the module set required for that ID. An app could store this mapping on the server allowing the frontend to include only the load ID in its request and have the server figure out which modules to send back. Internal serving infra uses module sets like this so this change allows easier integration into that tooling. Dart2js already supports emitting this deferred mapping JSON and internal infra is using that today. Other changes include: - Run the deferred loading transformer after TFA. This will exclude unused libraries in the resulting deferred loading map. Mark deferred helpers as entry points so that they don't get tree-shaken. - Some changes to naming conventions of JS helpers. - Use filename as module name to simplify JS helpers Change-Id: I5e2f5e374de77c87095d08bfff6534506cb10652 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/454240 Reviewed-by: Martin Kustermann <kustermann@google.com> Commit-Queue: Nate Biggs <natebiggs@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.