VS Code extensions v3.112

228 views

Skip to first unread message

Danny Tuppeny

unread,

Jun 2, 2025, 7:43:02 AMJun 2

to flutter-...@googlegroups.com

Hi all,

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

DevTools / Widget Inspector Embedded in Sidebar

#5469: Using DevTools in the sidebar no longer requires an experiment flag. By default, the Inspector page will be shown in the sidebar but this can be changed with the dart.devToolsLocation setting:

// Customise which sections are shown in the sidebar, in an editor tab, or external browser.
"dart.devToolsLocation": {
	// Default values are to show the Inspector in the sidebar and others
	// beside the code editor.
	"inspector": "sidebar",
	"default": "beside",
},

Inline Values During Debugging

#5426: When using the recently-released Dart 3.8 / Flutter 3.32, “inline values” will show for local variables and parameters during debugging.

Additionally, the experimental setting "dart.experimentalInlineValuesProperties": true will enable inline values for getters (be aware that invoking getters may have side-effects in your program). If you try this feature out, please provide feedback on GitHub.

Editor

#2785: You can now Ctrl+Click/Cmd+Click Pub package names in pubspec.yaml to open the related page on pub.dev. Additionally, @FMorschel contributed a similar feature to Ctrl+Click lint names in analysis_options.yaml to open the related documentation on dart.dev.

Testing

#5480: When developing in the Dart SDK repository in packages that use package:test_reflective_loader (such as analyzer or analysis_server), the Go to Test actions now navigate to the test method instead of the call to defineReflectiveTests. When a test fails, the error popup will also show at this new location.

Misc

#5515: The minimum version of VS Code for this version of the extension has been reduced from 1.96 to 1.75.
#5509: Recommendations for extensions (such as the Arb Editor) are no longer shown if the extension is already installed and enabled.

Experimental Features

#5516: Debug sessions can be started automatically when opening a project by adding launch configurations in a file .dart_tool/autolaunch.json. The format of this file is exactly the same as .vscode/launch.json. This feature is experimental and may change over coming releases.

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.

#5507: @FMorschel contributed a fix to prevent code completion from incorrectly triggering inside dartdocs.
#5505: Labels in source code and now assigned the label SemanticTokenType allowing them to be themed or customised.
#5201: try/catch/finally blocks are now foldable.

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!