VS Code extensions v3.116

237 views

Skip to first unread message

Danny Tuppeny

unread,

Jul 31, 2025, 10:20:05 AMJul 31

to flutter-...@googlegroups.com

Hi all,

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

Code Coverage for Flutter tests

#2860: It’s now possible to run tests while capturing coverage in Flutter projects. The “Run With Coverage” option appears in the test runner toolbar as well as against each individual test suite/test.

It also appears on the menu from the test gutter icons.

Coverage data will show in the gutter, and expand to highlight lines when hovered over. It’s also shown in the Explorer tree and the Test Coverage when on the Testing sidebar.

Flutter

#5612/#5617: Adding a Flutter project to a workspace that previously contained only Dart projects will now prompt to reload in order to switch to a Flutter SDK and start required Flutter services.
#5606/#5610: Interaction with Flutter’s device daemon has been switched to newer APIs, avoiding “No devices found” on Flutter’s master branch.
#5591: The Flutter: New Project command no longer shows the “Skeleton” option that was removed in Flutter 3.29.

Dependencies Tree

#5589/#5590: The Dependencies tree now includes an “Open on Pub” command on the context menu to quickly open the pub.dev page for a package.

Tasks

#5572: @mernen contribute a fix for background task patterns for the pkg:build_runner tasks.

Debugger

Dart-Code Extension API

#5008/#5583/#5595/#5601: New APIs are now exported by the extension to allow other VS Code extensions to reuse some of Dart-Code’s functionality. The internal private APIs that were intended only for testing (but had been adopted by some extensions) will be removed in an upcoming release. If you maintain a VS Code extension that uses these APIs, please see https://github.com/Dart-Code/Dart-Code/issues/5587 and ensure your extension is migrated.

Misc

#5586: An issue in the Dart SDK that could result in “The system cannot find the file specified” when tests has been resolved.
#5581: An improved error message is shown if you try to use a Dart SDK built for a different architecture.
#5604/#5607: Dart-Code’s own test files can now be run individually using npm run test src/test/path/to/test_file.test.ts.
#5614/#5615: The autolaunch.json functionality now supports waiting for a VM Service to become available before starting the debug session.
#5621/#5622: The autolaunch.json functionality now supports watching for modifications to the autolaunch file instead of only creation.
#5613: An environment variable DART_CODE_SERVICE_ACTIVATION_DELAY can now be used to delay the activation of background services like the Dart Tooling Daemon.
#5585: The Dart SDK’s MCP server is now enabled by default when available.
#5556/#5577: A new setting dart.mcpServerLogFile allows logging communication with the Dart SDK MCP server.
#5471: Many fixes have been made to Dart SDK tests that would previously fail when run through the VS Code test runner.

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.

#5588: Ctrl+Click to open the pub.dev page for dependencies listed in pubspec.yaml now works for the dependency_overrides section in addition to dependencies/dev_dependencies.

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!