VS Code extensions v3.130

60 views

Skip to first unread message

Danny Tuppeny

unread,

Mar 3, 2026, 5:20:50 AM (4 days ago) Mar 3

to flutter-...@googlegroups.com

Hey all,

New versions of the VS Code extensions have been published to the VS Code and OpenVSX marketplaces. Release notes are below (and online).

Testing

#5904, #5932, #5928: Tests are now marked as queued when starting a test debug session.
#5930: Running tests no longer sometimes cause “Cannot read properties of null (reading ‘startsWith’)” errors in the console and tests not to show up in the Test Results pane.
#5934/#5937: Test discovery is now much faster in large projects, particularly when disk access may be slowed by antivirus scanning.
#5935: package:test version detection (used to enable features like coverage) no longer fails if dart run test:test --version produces additional output (such as package fetching).
#5949: Test suites no longer sometimes show up as if they are skipped tests in the Test Results pane.
#5902: Tests that use package:test_reflective_loader are now grouped in the test runner by class (requires package:test_reflective_loader v0.6.0).

Editor

#5894/#5896: The Go to Imports action no longer targets a different editor/group if the target file is already open elsewhere.
#5913/#5914: The Add Dependency fix now correctly appears to move a dependency from dev_dependencies to dependencies when used in public files.
#5918: Highlighting of new and factory is now consistent between the textmate grammar used for intial syntax highlighting and semantic tokens that are laid on top.
#5920: The textmate grammar has been updated for the upcoming Primary Constructors feature.
#5135: Various changes have been made to make the display of getters and field more accurate. Many places that would previously fields will now correctly show the implicit getters they produce.

Flutter

#5948: Requests for emulators/platforms are no longer sent to the Flutter device daemon before device management is enabled. This might reduce the frequency of timeouts of those requests.

Commands

#5907/#5908: Pub commands like Get Packages for All Projects will now run multiple fetches in parallel, up to half the number of processors on the machine.

Misc

#5909/#5910: Extension startup no longer fails if .dart_tool/package_config.json contains invalid file paths for the current platform (for example because it was copied/cloned from another platform).
#5906: Extension activation no longer fails on realpathSync.native with some kinds of mounted drives.
#5911: Support for SDKs prior to Dart 3.2 / Flutter 3.16 (which previously produced a warning about being deprecated) has been removed. A table showing which extension versions support which SDKs (and instructions on how to change extension version) is available on the SDK Compatibility page if you need to continue to use an unsupported SDK.
#5924: Some CI bots have been enabled to run Dart-Code’s automated tests against Antigravity.

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.

#5933: Stack traces are now shown in the exception popups when the stack trace might not be the same as where the debugger is paused (for example when errors are rethrown or Completer.completeError() is used).
#5919: Factory constructors no longer sometimes appear as “<unknown>" in the breadcrumb/outline.

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!