VS Code extensions v3.142

93 views
Skip to first unread message

Danny Tuppeny

unread,
Sep 1, 2026, 7:11:28 AMSep 1
to flutter-...@googlegroups.com
Hi all,

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

Flutter

  • #6054: With the recent stable release of Flutter, the “Add a name to the constructor” and “Add a prefix to the import” refactors now prompt for a name rather than inserting a server-generated name.
  • #6134/#6140: Deep-links into DevTools (such as into the Widget Inspector when Overflow errors occur) are once again supported. When such an error occurs, a toast notification will offer a button to open a DevTools page an jump to the correct widget/location.

Debugging

  • #6133: The “Starting debug session…” text no longer appears for much longer than intended when running tests that produce no output.

Misc

  • #6141: A previous workaround to avoid issues when Flutter called git caused by the Copilot extension mutating environment variables has been removed, since the Copilot extension shipped a fix back in June.
  • #6110: Due to Firebase Studio being sunset, support has been removed.

Fixes enabled with Future VS Code releases

#6155: Errors like “Quick Fix failure: _dart.applySnippetTextEdit command not found” when using quick-fixes and code actions have been resolved in the upcoming v1.136.0 release of the VS Code editor (not the Dart extension).

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.

#6092/#6108: Refactors that use the new input framework (such as “Add a name to the constructor” and “Add a prefix to the import”) will now perform validation during typing instead of waiting for submission. Errors will suppress submission whereas warnings do not.

  • sdk#64030: The “Fix All in Workspace” commands now include the same Pubspec fixes as dart fix (for example adding missing dependencies).
  • sdk#64029: The “Fix All in Workspace” commands are now iterative and make multiple rounds of fixes, just like the single-file “Fix All” command/code action.
  • #6143: The color preview/picker has been updated to detect the withValueswithAlphawithRedwithGreenwithBlue methods on Color instead of just showing the base color prior to the invocation.
  • #6142: The new dartdoc example format {@example ...} now produces clickable links, like the previous “See code in …” format that was used in the Flutter SDK.
  • PR : Add support for client-side regex validators in interactive forms.
  • #2391: “Add to watch” and debug console evaluation now support multiline expressions, instead of only evaluating the first line.

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/

Reply all
Reply to author
Forward
0 new messages