For instructions on installing the Dart or Flutter extensions, go here.

v3.132.0 2026-03-31

Flutter

• #5995/#5982/#5971: Flutter initialization is now checked on each project load, avoiding issues where the Flutter SDK could overwrite the Dart SDK while other services were starting up.
• #6015/#6016: Closing Flutter workspaces (or VS Code) no longer sometimes show “Stopping extension hosts” for up to 5s. This was caused by a combination of a race condition when shutting down the Flutter daemon, and a regression in VS Code that blocked the UI instead of letting the extension host shut down in the background.

Testing

• #5953/#5991: Package nodes in the Test Explorer now include a Run Tests action to run all tests within that package.
• #5922/#5987: Integration test gutter icons no longer jump to incorrect locations when running on remote devices like Android.
• #5984: setUpAll/tearDown gutter icons are now correctly set to the queued state at the start of a test run.
• #5938: Tests skipped because they do not match a solo run no longer show Skip: does not have "solo" in Test Results (the same for the Debug Console requires an SDK update).
• #5931: Tests skipped because of solo now retain the correct locations.

Editor

• #5968: The Add ‘package’ to dependencies quick-fix now appears above Ignore quick-fixes.
• #5943: The dart.lineLength setting is now marked as deprecated. Use the formatter.page_width setting in analysis_options.yaml instead.

Commands

• #5917/#5996: Running Pub Get from an explicit save or the Get Packages button now shows output in the same Output channel.
• #5973: Fetching packages in Pub Workspaces that contain both Dart and Flutter projects no longer sometimes fails if FLUTTER_ROOT is set to an invalid Flutter SDK location.
• #5978/#5990: Get Packages for All Projects no longer runs redundant fetches for packages that are in the same Pub Workspace.
• #5997/#6000: Pub Get and Pub Upgrade commands now resolve packages to the containing Pub Workspace (if applicable) before executing.
• #5979: Output channels now include both the package name and containing folder names (package:foo (my_project/application1)) except where they are the same to reduce ambiguity for packages like example.

Performance

• #5936/#5983: Test capabilities are now computed from .dart_tool/package_graph.json instead of running dart test --version for each package, which can consume a lot of CPU/RAM during test discovery in large workspaces.
• #5951: Disk I/O during project searching and test discovery has been reduced, improving speed particularly when file access is slowed by antivirus scanning.

Misc

• #5965/#4617: @Peter080202 contributed a GitHub Action that checks all hyperlinks across the project are valid to avoid broken links.
• #5974/#5976: A lot of legacy code relating to SDK versions that are no longer supported has been removed.
• #5972/#5975: Many settings in the Legacy section that only applied to SDK versions that are no longer supported have been removed.
• #5977: Running Dart-Code’s debug tests locally no longer show an error about a terminal session terminating unexpectedly.
• #5945/#5966: Some of Dart-Code’s integration tests now run against Antigravity on the GitHub bots.
• #5944: The warning Possible EventEmitter memory leak detected. 11 terminated listeners added to [DartDebugClient] no longer appears when running Dart-Code’s tests.
• #5925/#5964: A lot of unrelated noisy output from VS Code is now filtered from the output of running Dart-Code’s tests.

Features/Fixes Enabled with Future SDKs

The following items depend on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They may be available to test in the current beta/master channels and will show up in future SDK releases.

• #5942: The --web-define flag is now supported by flutter run --machine which is used by IDEs to launch debugging sessions.
• #4670: Matching implementations and overrides of class members are now highlighted correctly when the text cursor is in one of them.
• #5938: Tests skipped because they do not match a solo run no longer show Skip: does not have "solo" in the Debug Console (the fix for Test Results is already live in this extension version).

Upstream Issues

Some feature requests and fixes require new features and fixes in upstream projects like VS Code and LSP which use counts of 👍s on those issues to help gauge demand. The Dart-Code website now lists some of the most significant upstream issues with a description of the feature/fix they would enable. Please consider reviewing this list and adding your 👍 to any GitHub issues relevant to features you’d like to see!

https://dartcode.org/upstream-issues/