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

v3.146.0 2026-10-29

Testing

• #6243/#6245: Integration tests across multiple projects no longer run concurrently. This caused problems on devices that can only run a single app at once, with one test session interrupting the previous.
• #6215/#6244: Workspaces with nested folders no longer trigger duplicate test sessions that can interrupt each other or fail to report results.
• #6247/#6268: Cancelling a test run from the Cancel button on the Test Explorer now works as expected.
• #6246/#6269: When multiple sequential test sessions are required to run many (or all) tests without debugging, a cancellable progress notification is shown to allow cancelling the entire batch.
• #6219/#6230: Some cases where renaming test files left stale entries in the Test Explorer have been resolved.

Editor

• #4982: Some code-folding issues with multiline strings in test() calls have been resolved.
• #4949: Hovers now show the source of a symbol (“Declared in Foo in bar/baz.dart”) in more cases.
• #6223/#6227: A cache has been added for the textDocument/documentOutline LSP request to prevent duplicate computation in the analysis server when VS Code requests the outline for multiple features (such as breadcrumb, outline view).

Flutter

• #6222/#6229: The internal widget preview project no longer shows up in the project/package picker (for example when triggering “Pub Get” outside of the context of a particular project/package).
• #6206: The .widget_preview folder used for the internal widget preview is now excluded from VS Code search results/file picker by default.
• #6200: Some edge cases where we might continue to spawn the widget preview server when the extension is shutdown during startup have been resolved.

Debugging

• #6249/#6250: Expanding an object with a deep inheritance chain in the legacy web debug adapter no longer collects getters into an exponentially growing list before de-duping.

Commands

• #6231: Prompts to run pub get and pub upgrade now include more specific messages, naming the package (or count) or other reason for needing to run.

Dart Tooling Daemon

• #6225/#6228: As a workaround for sdk#64641, the working directory when spawning DTD is now explicitly set to the first Dart package in the workspace. This ensures dart tooling-daemon list reports a folder that indicates which project/workspace it corresponds to. A proper fix will ship in an future Dart/Flutter SDK that lists all workspace folders.

Misc

• #6214: When trying to determine if a folder is a valid Dart SDK, we no longer rely on the file bin/snapshots/analysis_server.dart.snapshot. This snapshot is no longer used and is due to be removed from a future Dart SDK.
• #6207/#6208: A new setting dart.analyzerSessionLogFile allows enabling the analysis server session log (a log intended to replace the instrumentation log).
• #6209: An issue with embedded DevTools failing to load (showing only a grey panel) was fixed in VS Code v1.141.

CI / Testing

• #6025: Many improvements have been made to the extensions test coverage.
• #6165: Many improvements have been made to the time taken to run all CI bots.
• #6153: Several flakes with the E2E playwright tests have been resolved.
• #6255: Code coverage is now collected and reported on PRs opened from forks of the Dart-Code repository.

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.

• #6147: When running tests, a summary of passes/fails/skips is now shown at the start of each test line along with a summary at the end (similar to the usual terminal output of running dart test).
• #1837: Code completion for URIs in directives now refreshes on each / so the completion list shows only the next segment rather than the full (potentially long, truncated) path.
• sdk#63294: Newer server-described refactors now support the “Refactor anyway?” prompt when the refactor would introduce new analysis issues.
• sdk#64534: The “Add name to Constructor” and “Add prefix to import” now correctly warn if the new name is already in use.

Raising Bugs/Feature Requests and Voting on Issues

If you encounter bugs or have suggestions for the extension, please file them in the [github.com/Dart-Code/Dart-Code repo](https://github.com/Dart-Code/Dart-Code/issues). Please add 👍s to existing issues you would like to see implemented to help us prioritize.

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/