VS Code extensions v3.108

351 views

Skip to first unread message

Danny Tuppeny

unread,

Apr 1, 2025, 5:38:54 AMApr 1

to flutter-...@googlegroups.com

Hi all,

New versions of the Dart/Flutter extensions for VS Code have been published! Release notes are below (and online). Please post any issues or feedback to GitHub - thanks!

Experimental: DevTools Embedded in Sidebar

#5396/#5367/#5466: A new experiment allows embedding DevTools pages inside the sidebar instead of as editor tabs. Trying this out requires enabling an experiment flag and then using the hidden value "sidebar" in the dart.devToolsLocation setting:

// Enable the experiment
"dart.experimentalSidebarDevTools": true,
// Customise which sections are shown in the sidebar, in an editor tab, or external browser.
"dart.devToolsLocation": {
	"inspector": "sidebar",    // Embed inspector in sidebar
	"default": "beside",       // Default other tabs to an editor tab beside the current code editor
	"cpu-profiler": "external" // Open the CPU profiler in external browser
},

Please provide feedback on this feature in the Dart-Code repository on GitHub. Existing known issues can be found here.

Testing

#5456: Because the Dart SDK repository now uses Pub Workspaces, the dart.experimentalTestRunnerInSdk setting has been removed and the test runner functionality is available when working in the Dart SDK repository automatically.

Terminal

#5442: Invalid .dart_tool/package_config.json files no longer cause unhandled exceptions that could prevent other packages from being detected correctly for creating clickable links in the terminal.

Misc

#5447/#5448: @davidmartos96 contributed a fix to prefer launching studio over stduio.sh when started Android Studio to avoid a warning when Android Studio opens.
#5458: The analysis server diagnostic pages and exportable report now include some useful values from the VS Code settings (such as whether formatting or other code actions are enabled on-save).
#5433: The extension no longer tries to inject settings into all configuration provided to the server, regardless of whether it’s the Dart configuration or not.
#5090: The dart.previewDtdLspIntegration setting has been removed and the analysis server will now always connect to DTD when using a supported SDK version. If you are interested in integrating with the analysis server over DTD please see this issue about capabilities.

Documentation

#5453: The description of the toolArgs launch configuration field has been updated to not use dart run as an example, as Dart scripts are currently launched by the debug adapter without run.
#5431: The Dart: DevTools Browser setting is now documented as only working for local workspaces. Remote workspaces always use the default browser.

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.

#5426/#5444: When debugging on the latest SDKs, “inline values” will show for local variables and parameters.

Additionally, enabling the hidden setting "dart.experimentalInlineValuesProperties": true will show inline values for getters. If you try out these features, please provide feedback on GitHub (useful feedback includes where values may appear unexpectedly, or expected values not showing up).

#3948: Due to changes in Flutter to write localizations into your own app, localizations will no longer sometimes be missing from code completion/quick fixes.

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!