commit | e20dc20543df953b29666ff61a6e562c9e91fea2 | [log] [tgz] |
---|---|---|
author | Martin Kustermann <kustermann@google.com> | Fri Jul 19 07:53:01 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 19 07:53:01 2024 +0000 |
tree | dd658bff78312837f3b3c15f140a4180b6b03d04 | |
parent | 35a595f66b2f55deb88e88f12fb7b89e622d26cc [diff] |
[beta] [dart2wasm] Generate source maps This implements generating source maps for the generated Wasm files. Copying dart2js's command line interface, a source map file with the name `<program name>.wasm.map` is generated unless `--no-source-maps` is passed. When a source map is generated, the generated .wasm file gets a new section `sourceMappingURL` with the contents `<program name>.wasm.map`. This section seems to be undocumented, but Chrome and binaryen recognize it as the URI to the source map file. Chrome is then loads it automatically in the DevTools. - `wasm_builder` package is updated with the new `source_map` library, which describes the source mapping entries. - `wasm_builder`'s `InstructionsBuilder` is updated with the new public members: - `startSourceMapping`: starts mapping the instructions generated to the given source code. - `stopSourceMapping`: stops mapping the instructions generated to a source code. These instructions won't have a mapping in the source map. - `CodeGenerator` sets the source file URI and location in the file when: - Starting compiling a new member - Compiling an expression and statement Bug: https://github.com/dart-lang/sdk/issues/55763 Change-Id: Ieb24796b4b17a735b846793617664a453f1061ce Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/370500 Cherry-pick-request: https://github.com/dart-lang/sdk/issues/56239 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/375660 Reviewed-by: Ömer Ağacan <omersa@google.com> Commit-Queue: Martin Kustermann <kustermann@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.