| commit | 03b4beba2dae8e139927397086133081f6e5771a | [log] [tgz] |
|---|---|---|
| author | Daco Harkes <dacoharkes@google.com> | Tue Oct 14 07:07:31 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 14 07:07:31 2025 -0700 |
| tree | 59a7bf5177712f6c5c10170c1bfe0c3c34aa35df | |
| parent | 94670bffc27d8233f94a77199e2803a5c4c8ff78 [diff] |
[beta] [dartdev] Progress updates for running hooks Issue description: When running dart run and dart test no feedback is visible in the terminal that something is happening. With long-running hooks this leads to the users wondering if their dart process is hanging. What is the fix: Print in the console a timer counting up. Why cherry-pick: Dart 3.10 stable makes build hooks generally available Risk: Low. The implementation in dartdev is fairly simple. Shows a progress update on the interactive terminal for running hooks. The progress update visually aligns with progress updates from pub `Building package executable... (1.3s)` as `Running build hooks... (0.7s)`. Closes: https://github.com/dart-lang/native/issues/2439 Progress updates visibility: * `dart run`, only if there are hooks to avoid cluttering stdout more. https://github.com/dart-lang/sdk/issues/61696 * `dart test`, also only if there are any hooks. * `dart build`, always show progress update lines. * `dart install`, always show progress updates lines. * `dart compile`, changed the check to check for the existence of hooks but don't ever run them. This CL also renames some "native assets" to "build hooks". This CL also fixes an issue with `dart test` run without `pub get` in a Flutter project. Closes: https://github.com/dart-lang/sdk/issues/61697 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/453920 Change-Id: I88f6e07dff1d4f5c0733f83f073640b75cc54e79 Cq-Include-Trybots: luci.dart.try:pkg-linux-release-try,pkg-win-release-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/454300 Reviewed-by: Michael Goderbauer <goderbauer@google.com> Reviewed-by: Ben Konyi <bkonyi@google.com> Reviewed-by: Alexander Thomas <athom@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.