All Releases

v3.54.1 2022-11-30

#4290: Running the Pub: Upgrade Packages command will no longer sometimes run pub get instead of pub upgrade.

v3.54.0 2022-11-29

Improved Status Bar Information

#4257: Several items that used to have their own status bar entries have been merged into VS Code’s new language status area. This can be found from the {} icon next to the language in the status bar.

Clicking the “pin” icon against an entry will move it back to being always visible on the status bar.

Flutter: New Project Platform Defaults

#4284: When creating a new Flutter project using the Flutter: New Project command it’s now possible to set the default platforms that should be enabled for new projects. This can be accessed from the “cog” icon when entering the project name.

These can also be set directly via the dart.flutterCreatePlatforms setting.

Flutter

#4089: cmd/ctrl+click is now supported on file:// and package: links in the test error peek window.
#4283: The Flutter: New Project settings editor now pre-selects the existing selected values in single-selection lists.
#4276: The Hot Reload button and commands are now hidden if running your app in Profile/Release mode.
#4272: The entries for enabling new platforms in the device selector are now listed after a seperator to make them easier to find.
#4249: Chrome will no longer fail to be located if defined by CHROME_EXECUTABLE when using the new SDK debug adapters.

Editor

#4255: A new command Dart: Toggle Line Comment Kind has been added that cycles through no comment, double-slashes, triple slashes.
#4253: An issue that prevented Pub package names (used by the Dart: Add Dependency command) from being cached locally has been resolved.
#3547: The dart.showTodos setting now accepts an array of strings and can be used to individually choose which TODO-style comments (of those supported by the analyzer - TODO, FIXME, HACK, UNDONE) should be shown. This requires Dart SDK >= 2.18.

Commands

#4261: Upon opening a project, if your Dart/Flutter SDK versions have changed since you last ran pub you will now be prompted to run pub upgrade.

Testing

#4163: Gutter icons for helper methods that call setUpAll/tearDownAll will no longer appear on the wrong line.
#4286: setUpAll and tearDownAll results will no longer appear as runnable tests (which error if attempted to run). They still appear in the gutter/test tree to indicate their success/failure, but have no Run or Debug actions.

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 will show up automatically after you upgrade to the next (non-hotfix) Dart/Flutter SDK release. If you’re using a recent beta or master version, these items should be available to you and any issues should be reported on GitHub in the usual way.

#4279: Some quick-fixes are now available for pubspec.yaml and analysis_options.yaml files.
#4119: A new setting dart.documentation allows selecting what level of documentation (none, summary, full) should appear in hovers and code completion. The default is full to match previous behaviour.
#4268: A new ‘Application (empty)’ template is available when creating Flutter applications which is a stripped down version of the standard ‘Application’ template without all of the explanatory comments and test stubs.
#4136: Use of Container() has been changed to Placeholder() in many Flutter snippets.
#4116: Code completion for overriding methods now includes members that have unimported types in their signature. Additionally, code completion now supports adding multiple imports automatically to support the case where there are several unimported types in an override completion from different libraries that are not yet imported.
#3787: Code completion now shows correct constructor documentation for class constructors that are not yet imported into the current file.
#4144: Unimported extension members now show their documentation correctly in code completion.
#4242: Several issues with nested/overlapping code folding have been addressed.
#4269: Whole functions can now be folded (both parameters and body) in a single region.
#4243: ‘.dill’ files will no longer sometimes be created alongside test files during test runs.
#4185: The ‘Create Missing Overrides’ fix no longer includes invalid non-nullable types in the selector for choosing types.
#4275: Analyzer plugins can now provide code completion entries that automatically import libraries.
#4128: Dart SDK sources are now correctly mapped when running Flutter applications using the new SDK debug adapters (currently behind the "dart.previewSdkDaps": true flag, but enabled by default for pre-release SDK users).

v3.52.1 2022-11-02

#4239: An issue introduced with #4197 that could prevent cwd being inferred correctly in multi-root workspaces when program was a relative path has been resolved.

v3.52.0 2022-11-01

Debugger

#4197: When launching debug sessions, if an explicit program is supplied but no cwd in the launch configuration, only the program (and not the current open file) will be used to determine the best working directory.
#4209: Mapping call stacks while debugging has been optimised in a way that avoids some calls that could fail when running Flutter apps on the web using the current stable Flutter SDK (an issue that has been fixed for future Flutter SDK releases).

Flutter

#4093: A new command Flutter: Inspect Widget (Auto-Cancel after Selection) behaves the same as Flutter: Inspect Widget but will automatically exit selection mode upon after selecting a widget and navigating in code.

Editor

#4229: The legacy Type Hierarchy command no longer shows up in the command palette when using LSP (where it does not work). Integration with the new VS Code built-in Type Hierarchy will be available when using LSP in an upcoming Dart/Flutter SDK release (see below).

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 will show up automatically after you upgrade to the next (non-hotfix) Dart/Flutter SDK release. If you’re using a recent beta or master version, these items should be available to you now and any issues should be reported on GitHub in the usual way.

#4221: Refactorings like “Convert Getter to Method” no longer appear on references to symbols outside of your workspace which made it possible to accidentally modify Flutter SDK or Pub package sources.
#4202: The “Extract Method” refactor no longer shows up on import statements.
#4165: The “Extract Method” refactor no longer shows up on method declarations.
#4215: Renaming enum constants will no longer sometimes show “The element can’t be renamed”.
#4214: Changing the "dart.showTodos" setting now applies immediately rather than only when a file is next modified (or a VS Code reload).
#4203: Quick fixes in the lightbulb menu are no longer sometimes ordered incorrectly with // ignore: fixes appearing further up the list than intended.
#4156: Inlay hints for types (shown while holding Ctrl+Option/Alt) can now be hovered to see documentation for that type.
#2527/#3313: VS Code’s built-in Type Hierarchy is now available (when using LSP) and can be found in the context menu.
#4217: The new Type Hierarchy now includes Type Arguments in labels.
#4206: Expression evaluation is now available in the Debug Console when running Flutter integration tests.
#4213: Lists from dart:typed_data like Uint8List are now rendered as lists (rather than objects) in Watch/Variables panels when using the new SDK DAPs.
#4204/#4205: Large lists in Watch/Variables panels are now paged when using the new SDK DAPs, avoiding long delays/hangs when trying to expand very large lists.

v3.50.0 2022-10-03

Flutter

#3808: Attaching to a Flutter process started outside of VS Code no longer requires manual configuration of the packages file in order for the debugger to correctly locate files while debugging/stepping. This fix applies only to the new SDK DAPs (which can be opted-in to using the dart.previewSdkDaps setting).

Editor

#4152: The “Run”/”Debug” CodeLens links now appear on the line directly above the main method name, and not above the related DartDoc comments.

Other

#4178: In a multi-folder workspace, running a debug session without an explicit cwd or one that can be inferred from program will now use the nearest common ancestor of all open workspace folders (if one can be found that is not the drive root).
#4134: When using the Dart: Capture Logs commands, long lines are no longer truncated. Logs written to disk using the related settings are still truncated based on the dart.maxLogLineLength setting.

Rollout of New SDK Debug Adapters

#4194: Several issues that led to pausing the rollout of the new SDK debug adapters have been resolved in latest bleeding-edge builds of Dart/Flutter. As such, rollout will continue when using an SDK version with these fixes (which is currently only users of the Flutter/Dart master branches).

Additionally, users of pre-release SDKs (with a sufficient version number to include the fixes noted above) will immediately be opted-in to the new DAPs (skipping the progressive rollout used on the stable branch). If you notice any unexpected behaviour while debugging (or while not debugging 🙂) please file issues which as much detail as possible!

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 will show up automatically when you update your SDK in future (or sooner if using beta/development channels - depending on the exact version).

#612: Call Hierarchy is now available (Shift + Alt/Option + H, or from the context menu).
#4154/#3609/#4160: Inlay hints are now available for inferred types and parameter names (shown while holding Ctrl + Alt/Option).
#4143: Auto-imports now work when completing extension members.
#4131: Renaming a symbol no longer updates DartDocs with unresolved identifiers of the same name.
#4129: Go to Symbol in Workspace no longer navigates to the parent library file when using parts.
#4121: Code folding regions that overlap the same line (such as parameter list and function bodies) have been adjusted since VS Code recently stopped supporting them.
#4120: Hovering over a constructor’s parameters no longer show an oversized font for the type.
#4114: Navigation/resolution of DartDoc qualified references that reference members from a base class now work as expected.
#3182: Code completion now offers members that can be overridden when invoked in a completely empty class.
#4184: The Create missing override(s) quickfix now shows in completely empty classes.
#4181: Links for the “See code in” example links in Flutter no longer return additional unexpected results when trying to navigate with Go to Definition / ctrl + click.
#4169: The Remove widget assist is now available on widget calls prefixed with aliases.
#4167: The Inline Method refactor no longer fails if the method has type parameters.
#4157: Find References once again works when the caret is at the end of the symbol name (or the entire symbol name is selected). This issue only affected some recent pre-release versions of the SDK.
#4141: Hot Reload and Hot Restart now show progress notifications when using new SDK DAPs.
#4101: The Debug Console now focuses more quickly when launching an app using the new Flutter SDK DAP.
#3966: DevTools no longer sometimes fails to open if a previous window had been closed within the last 30 seconds.
#4149: Breakpoints will no longer fail to be hit on Windows when using SDK DAPs depending on the casing of the drive letter of the current working directory.

v3.48.4 2022-09-16

#4162: The Inlay Hints setting has been overridden from VS Code’s default of “on” to “offUnlessPressed” for Dart. This prevents inlay hints showing up automatically for users on bleeding-edge/master SDKs that have support for this feature.

v3.48.3 2022-09-07

Rollout of the SDK DAP for Flutter has been postponed due to a number of crash reports (https://github.com/flutter/flutter/issues/111045). The Flutter SDK DAP can still be enabled with "dart.previewSdkDaps": true but automatic rollout is paused.

v3.48.2 2022-09-06

#4147: Rollout of new SDK debug adapters has been disabled for Windows users while an issue with breakpoints not working is addressed. All Windows users will continue to use the original debug adapters until this issue is resolved, when the rollout will resume.

v3.48.1 2022-09-05

#4139: The Flutter: Hot Reload and Flutter: Hot Restart commands are no longer missing (and with them, reload-on-save functionality) when running without debugging if using the new SDK DAPs.

v3.48.0 2022-09-01

Folder Renames

#2483: When using Flutter 3.3 / Dart 2.18, moving or renaming a single folder will now update import statements the same way renaming a single file will. Renaming/moving multiple files/folders at once is not currently supported.

Flutter

#3015: The “Wrap with widget” refactor now sets the selection to widget ready to type a widget class name.
#4061: The other “Wrap with …” refactors now set the caret position to the opening paren rather than the closing paren (which may be many lines below).

Debugger

#4074: Adding breakpoints in files that will not be hit because of debugger settings will now show a prompt even if debugger settings have previously been customised.

New Debug Adapters for Dart and Flutter

New debug adapters (which provide the interface for VS Code to communicate with a running Dart/Flutter app) are available when using Flutter 3.3 / Dart 2.18. These new adapters are written in Dart provide some bug fixes and performance improvements over the original Dart-Code TypeScript adapters and will be easier to maintain/fix going forwards.

Users will be switched to the new adapters gradually over the coming releases, but they can be explicitly enabled/disabled by setting the dart.previewSdkDaps setting to true (opt-in) or false (opt-out). If not set (undefined), the extension will decide when to enable the new adapters.

Some initial improvements in the new adapters:

#4066: Running a Flutter app using “Run”/”Run without Debugging” no longer requires an active connection to the VM Service on the device running the app.
#3551: Breakpoints set in Dart SDK libraries by navigating with Go-to-Definition are now supported for Dart applications (not yet for Flutter apps).
#3522: Stepping through Dart SDK files when debugging Dart apps no longer opens duplicate copies of the SDK libraries (not yet for Flutter apps).
#3921: Detaching from an attached Flutter process will remove breakpoints and automatically resume.

If you notice any unexpected differences when using the new SDK DAPs, please file an issue. You can tell whether you’re using the new SDK DAPs by using the Capture Debugging Logs command before launching your app and checking whether the log contains “Running SDK DAP” instead of “Running debugger via node”.

Editor

#4112: The “You are modifying a file outside of your open folders” warning will no longer appear for non-Dart files.
#4097: The dart.useLsp setting has been replaced by dart.useLegacyAnalyzerProtocol and its meaning inverted. This setting will be removed in a future version. If you find that you need to enable use of the legacy protocol, please file an issue detailing why.

Testing

#4125: Tests with more than one newline in their names will no longer fail to run from CodeLens links.

Other

#4110: The dart.runPubGetOnPubspecChanges setting has changed from a boolean to support “always”, “prompt”, “never”. The new “prompt” setting will force a prompt to be shown when pubspec changes before fetching new packages.
#4080: The dart.customDevToolsUri setting added in the previous release has been replaced with a new dart.customDevTools which can launch a local development version of DevTools itself to aid debugging the embedded view if contributing to DevTools. Using this setting is documented in the DevTools contribution guide.

Documentation

#4126: Docs detailing all available launch configuration options have been updated to include templateFor.

Features Enabled with Flutter 3.3 / Dart 2.18

Many features and fixes that previously required using pre-release versions of Dart/Flutter are now available after upgrading to stable Flutter 3.3 and/or Dart 2.18 SDKs.

#3934: The ordering of diagnostics will now remain stable during typing (where the specific diagnostics do not change) to avoid VS Code’s Peek Error (F8) functionality from changing the selected error during typing.
#3929: Opening loose .dart files that are not part of a project (with a pubspec.yaml or analysis_options.yaml) will no longer sometimes cause some “File is not being analyzed” errors during startup.
#3906: Code completion for the named argument children: [] will no longer insert [] if completion is invoked on the children label and a value is already present.
#3892: Accepting code completion suggestions should no longer sometimes delete additional characters when the system is under load/slow.
#3833: Go to Type Definition allows navigating to the definition of a type of a symbol without first needing to navigate to the symbols definition.
#3952: Using source.fixAll in editor.codeActionsOnSave is no longer very slow (despite the command being very fast when run on its own).
#3975: Flutter Widget snippets now include return Container() as a placeholder build method.
#3981: “Add curly braces” now shows as a Quick-fix for the always_put_control_body_on_new_line lint.
#3970: Ctrl+Click/Go-to-Definition now works on filenames in “part of” directives.
#3950: Code Actions such as Dart: Sort Members and Organize Imports will now fail silently if configured to run on-save (via editor.codeActionsOnSave) and show errors if invoked manually.
#4020: Ctrl+Click on constructor declarations now automatically searches for references (depending on VS Code settings) as it already did for other types of declarations.
#4017: The fun snippet to create functions has been restored.
#4000: The Dart: Convert Method to Getter and Dart: Convert Getter to Method refactors will no longer show up in locations where they are not valid (and would error if selected).
#4029: The Dart: Extract Method refactor no longer shows up for import prefixes.
#4027: Code completion will no longer sometimes insert a literal (...) instead of parameter placeholders.
#3943: Code completion for symbols that start with $ that are not yet imported will no longer insert duplicate $s when selected.
#3945: Error messages shown when trying to launch DevTools for a build that does not support it have been improved.
#4039: When using SDK debug adapters (via the "dart.previewSdkDaps" setting or automatic opt-in described above), exception popups now include the full exception text (matching the existing debug adapters).
#4053: The Extract Method refactor no longer incorrectly adds the async keyword to synchronous code that contained asynchronous callbacks.
#4031: Several issues with Go to Definition not navigating correctly on super/this formal params have been resolved.

v3.46.1 2022-08-03

#4083: Certain formats of exclusion rules in analysis_options.yaml will no longer cause more folders than expected to be excluded from project detection.

v3.46.0 2022-08-02

Editor

#3055: Actions that cause the extension to reload the language server (such as modifying SDK settings, or changing the selected SDK) no longer generate errors like “edit.sortMembers is already registered”.
#4050: The default formatter for Dart files is now set explicitly. This prevents the Dart formatter from being disabled if another formatter sets itself as the global default. If required, this can be overridden by setting the editor.defaultFormatter setting inside the Dart-specific settings (“[dart]”).

Testing

#4042: Tests that include < or > in their names (but not immediately following quotes) no longer prevent tests from running using CodeLens links.

Debugger

#4076: After updating the path of a dependency (or switching between a path and other type of dependency) in pubspec.yaml and then Hot Restarting, the debugger will no longer continue to jump to the original sources paths when breaking/stepping in the dependency.

DevTools

#3944: A new setting "dart.customDevToolsUri" allows overriding the URI used when launching/embedded DevTools. This setting is intended for use by DevTools developers to simplify testing DevTools when embedded in VS Code.

Other

#4028: Nested projects excluded from analysis using analysis_options.yaml are now also excluded when locating projects, including when deciding whether to use a Dart or Flutter SDK. This prevents the Flutter SDK being selected for Dart projects that may include nested Flutter projects for testing purposes (such as the project for the linter package).

Features/Fixes Enabled with Future SDKs

These items rely on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They will show up automatically when you update your SDK in future (or if using beta/development channels depending on the exact version).

#4039: When using SDK debug adapters (via the "dart.previewSdkDaps" setting), exception popups now include the full exception text (matching the existing debug adapters). Migration to the SDK debug adapters by default will begin in an upcoming release.
#4053: The Extract Method refactor no longer incorrectly adds the async keyword to synchronous code that contained asynchronous callbacks.
#4031: Several issues with Go to Definition not navigating correctly on super/this formal params have been resolved.

v3.44.0 2022-07-01

Flutter

#3993: A new setting dart.flutterGenerateLocalizationsOnSave allows the Flutter: Generate Localizations command to be run automatically when a .arb file is saved.
#4036: The Wrap with widget refactor will no longer sometimes insert snippet placeholders like ${0:widget} in code.
#4002: The Wrap with… refactors will no longer sometimes remove escaping backslashes in the modified code.
#4007: Running Flutter tests with multiline names on Windows no longer fails with “No tests match regular expression ‘test & exit /B 0’”.
#4026: The Flutter: Check Elevations command has been removed because the underlying Flutter service was removed due to changes in layer positioning.

General

#4001: @blaugold contributed nesting pubspec_overrides.yaml under pubspec.yaml when explorer.fileNesting is enabled.
#3974: The default value of dart.projectSearchDepth has been increased from 3 to 5. This allows projects nested more deeply in your workspace to be found. Additionally, if the search for projects takes more than 1 second a progress indicator will be shown, allowing the search to be stopped early. Results from workspace searches are now also cached for a few minutes to improve performance.
#4011: Having folders from both Dart SDK repo and non-Dart SDK repo in the workspace no longer tries to use pub or dart test (which are not available for Dart SDK repo projects).
#3990: A new setting dart.runPubGetOnNestedProjects allows running pub get for nested parent/child projects when a pubspec.yaml is modified. This may be useful where you have nested projects with path dependencies (such as an example project) where both projects package_config.json files need regenerating when adding dependencies to one.

Testing

#4032: The Test: Run All Tests command no longer fails if the workspace contains integration tests that are not valid for the current device. Instead, they will be skipped.

Features/Fixes Enabled with Future SDKs

#3950: Code Actions such as Dart: Sort Members and Organize Imports will now fail silently if configured to run on-save (via editor.codeActionsOnSave) and show errors if invoked manually.
#4020: Ctrl+Click on constructor declarations now automatically searches for references (depending on VS Code settings) as it already did for other types of declarations.
#4017: The fun snippet to create functions has been restored.
#4000: The Dart: Convert Method to Getter and Dart: Convert Getter to Method refactors will no longer show up in locations where they are not valid (and would error if selected).
#4029: The Dart: Extract Method refactor no longer shows up for import prefixes.
#4027: Code completion will no longer sometimes insert a literal (...) instead of parameter placeholders (affected Dev builds only).
#3943: Code completion for symbols that start with $ that are not yet imported will no longer insert duplicate $s when selected.
#3945: Error messages shown when trying to launch DevTools for a build that does not support it have been improved.

v3.42.1 2022-06-01

#4003 v3.42.1 resolves an issue using bleeding-edge Dart/Flutter master where the language server could fail to start.

v3.42.0 2022-06-01

Dart: Add Dependency Improvements

#3811: It’s now possible to add multiple dependencies in one step using Dart: Add Dependency using commas between package names.

Flutter

#3998: New icons added in Flutter 3.0 (such as solar_power, safety_check) now have previews in hovers/completion.
#3997: CupertinoIcons.location no longer shows the wrong icon preview in hovers/completion.
#3949: A new Flutter task/command (Flutter: Generate Localizations) has been added (including in context menus/title bar for .arb files) that runs flutter gen-l10n.
#3961: Support for initializing the Flutter SDK when installed by a package manager has been generalised to support package managers other than Snap (such as Hermit).
#3968: The dart.flutterShowEmulators setting now has an additional value "never" which always hides emulators from device selection picklists.
#3971/#3965: @nilsreichardt contributed a fix to move the call to super.dispose() to the end of the dispose() method in the stanim snippet. Note: When snippets are being provided by the language server, the dispose() call will still be at the start of the method until the next Dart/Flutter SDK releases.

Editor

#3782: Documentation in hovers and code completion can now render basic HTML tags like <b>, <i>, <blockquote> .
#3989: File nesting patterns have been added to nest several generated files like pubspec.lock and .packages under the pubspec.yaml file and foo.g.dart under foo.dart. File nesting can be enabled using the explorer.fileNesting.enabled setting (and default state with the explorer.fileNesting.expand setting).
#3995: The dart.hotReloadOnSave and dart.flutterHotReloadOnSave settings have been updated to include new values "manualIfDirty" and "allIfDirty" that will trigger hot-reload-on-save only if the saved file(s) are dirty. The default value remains "manual" to better support auto-save. The "always" setting has been renamed to "all".
#3996: Code Actions that generate code with suggested names (such as Assign value to new local variable) no longer insert snippet markup text into the file.
#3969: Snippets like for no longer fail to appear in apps with large dependencies (including Flutter apps).
#3954: When using Dart 2.17/Flutter 3.0 with LSP disabled, snippets will no longer fail to show up.
#3946: If a language server request fails, the Output pane will no longer be automatically focused before clicking the “Go to Output” button.

Testing

#3963: Improvements have been made to the recording of test messages that show up in the Test Error Peek window for failed tests. The final failure message should now show up instead of a generic “The test failed” message.

DevTools

#3967: Using the dart.devToolsLogFile setting to log communication with the DevTools server no longer fails to record any traffic.

Docs / Website

#3994: Descriptions on the dart.sdkPath and dart.sdkPaths settings (and equivalent Flutter settings) have been improved tp make it clearer that the sdkPaths settings are used only for SDK switching and not for initial SDK searching.
#3824: Docs now contain additional examples for how to configured launch configurations for Dart (non-Flutter) web apps.

Features/Fixes Enabled with Flutter 3.0/Dart 2.17

A number of features/fixes noted from in previous release notes that relied on an updated Dart/Flutter SDK are now available to stable channel users that have upgraded to Flutter 3.0/Dart 2.17, including:

#3873: Code completion for zero-argument functions no longer places the cursor inside the parens.
#3872: The Extract Method code action will now check the extraction is valid before prompting for a method name.
#3869: Some code actions like Surround with if now have improved snippet support and will provide better selections after inserting code.
#3867: Holding ctrl when hovering over paths to examples in Flutter dartdocs will no longer highlight significantly more of the file than included in the path.
#3864: “A request has failed” errors will no longer appear if you navigate to files that reference Flutter colors that are outside of the workspace (such as Flutter SDK sources or Pub package sources).
#3846: The “Convert Getter to Method” assist now works for extensions.
#3844: Code completion no longer inserts unwanted commas when editing argument names.
#3823: A new “Convert to ‘package:’ import for everywhere in file” fix is available when using the always_use_package_imports lint.
#2492: The “Wrap with Column” refactor is now available when a Widget constructor is selected and not only when there is no selection.
#3830: The “Invalid file path” message sometimes shown when analysis fails will be more specific rather than a catch-all for several types of failure.
#3783: Code completion no longer activates while typing in standard double-slash comments that are immediately before a dartdoc triple-slash comment.
#3778: A new "instance" semantic token modifier has been added to instance members, allowing them to be themed/colored separately to other symbols.
#3770: The Create Method ‘xxx’ fix now includes the required keyword for required named arguments if the library is null-safe.
#1160: Hover tooltips now include the static type of a variable, which may be different to the declared type (for example if the variable is used in an is check).
#3784: Code completion should now include members that can be overridden more reliably.
#3440: New packages added to pubspec.yaml should now be available more reliably after saving and waiting for the *pub get command to complete.
#3438: Fetching packages in a Flutter project should no longer intermittently result in the flutter_gen package failing to resolve.

Features/Fixes Enabled with Future SDKs

#3952: Using source.fixAll in editor.codeActionsOnSave is no longer very slow (despite the command being very fast when run on its own).
#3975: Flutter Widget snippets now include return Container() as a placeholder build method.
#3981: “Add curly braces” now shows as a Quick-fix for the always_put_control_body_on_new_line lint.
#3970: Ctrl+Click/Go-to-Definition now works on filenames in “part of” directives.

v3.40.0 2022-05-02

Flutter

#3913: Previews for Flutter icons that begin with reserved terms (like try, class, new, switch) now appear correctly in Dartdocs.
#3912: When the flutter tool is run for the first time by the extension, the Output pane containing welcome text will remain visible instead of closing automatically.

Debugger

#3937: The Debug: Select & Start Debugging command now includes a launch configuration for each available device. Clicking the cog icon will create a specific launch configuration in launch.json for that specific device, regardless of the current selected device.
#3918: Hot Restart no longer sometimes causes errors to be written to the VS Code developer console when an application has more than one isolate.

Commands

#3924: The setting dart.flutterCreateOffline has been renamed to dart.offline and now passes --offline to other commands (such as pub get) in addition to flutter create.
#3920: A new setting dart.devToolsLocation replaces dart.embedDevTools to configure where DevTools should be launched. The default setting "beside" behaves the same as the previous embedding (opening in a tab beside the current editor). "active" open over the top of the current editor (which can be full-width). "external" opens in an external browser window.

Other

#3922: file:/// links for Dart files in the embedded terminal are now detected more reliably and should not lead to “Invalid file path” errors after clicking.
#3938: Activations of the Dart extension in workspaces that do not contain Dart/Flutter projects (such as when VS Code requests dynamic debug configs while working on another project) will no longer trigger Dart SDK update notifications.
#3919: Opening a project with no pubspec.yaml will no longer suppress the notification if a Dart SDK cannot be found.
#3933: The dart-lang/sdk repo is again detected correctly, disabling automatic pub get and related commands.

Features/Fixes Enabled with Future SDKs

Server-Provided Code Snippets

#3904: When using a new enough SDK, the local code snippets are suppressed and snippets will be provided by the Dart LSP server. Server-provided snippets are contextual and can adapt to your project settings and language version, including:

#2059: Only snippets that are valid at the current location are shown (for example the class or stful snippets are only shown at the top level, and if and switch are not shown at the top level).
#3347: Nullability suffixes ? are only included when null saftey is enabled.
#3899: Super parameters may be used when available.
#3582: List<String> args are not included in main() functions for test files.

Go to Type Definition

#3833: Go to Type Definition allows navigating to the definition of a type of a symbol without first needing to navigate to the symbols definition.

Flutter

#3921: When using the new SDK debugger implementations (dart.experimentalSdkDaps), detaching from a Flutter process will remove breakpoints and automatically resume.
#3837: The --multidex/--no-multidex flag now works correctly for launches of flutter run through the VS Code debugger (including defaulting to enabled).

Editor

#3934: The ordering of diagnostics will now remain stable during typing (where the specific diagnostics do not change) to avoid VS Code’s Peek Error (F8) functionality from changing the selected error during typing.
#3932: The var keyword is no longer highlighted differently when used in a for loop for some themes.
#3929: Opening loose .dart files that are not part of a project (with a pubspec.yaml or analysis_options.yaml) will no longer sometimes cause some “File is not being analyzed” errors during startup.
#3906: Code completion for the named argument children: [] will no longer insert [] if completion is invoked on the children label and a value is already present.
#3892: Accepting code completion suggestions should no longer sometimes delete additional characters when the system is under load/slow.

v3.38.2 2022-04-08

#3916 v3.38.2 resolves an issue where debug sessions could terminate prematurely after upgrading to VS Code 1.66 if breakpoints were set and the application spawns additional isolates.

v3.38.1 2022-04-05

v3.38.1 was a release of the Flutter extension only. It fixes an error reported in the VS Code developer tools console while activating the extension.

v3.38.0 2022-04-04

Flutter

#3859: Projects with no valid target platforms will no longer show as if every target platform is valid.
#3886: Several pick-lists in the UI that previously showed duplicates when there are multiple project folders open have been fixed.
#3881: The dart.flutterUiGuides color contribution now provides a default color for high contrast light themes.
#3879: Invalid values in the Flutter SDK version file no longer result in the extension failing to activate.
#3877: The Wrap with widget code action no longer shows literal snippet placeholders with $0 and $1 when using new (pre-release) SDK versions.
#3858: A new setting dart.projectSearchDepth controls how deep the extension searches in the open workspace for Flutter projects. If you do not see the Flutter device selector in the status bar and your Flutter projects are nested deeply, you may need to increase this value. Doing so may increase startup time.
#3870: Trying to launch Flutter projects in a workspace that is not in “Flutter mode” (see dart.projectSearchDepth above) now provides clearer message.

Editor

#3885: With new (currently pre-release) SDK versions, parameter hints will no longer fail to show automatically for some functions.

Debugger

#3884: Local variables in debug window are now sorted alphabetically.

Commands

#3882: Commands like Dart: Add Dependency now correctly detect the active project even if the Output pane has focus.
#3875: The Open Observatory Timeline command has been removed. The DevTools commands now provide access to the same (and more) information.

Testing

#3854: It’s now possible to override the Run/Debug launch configurations used by the Test Runner by specifying a "templateFor" field on a launch.json configuration. The value should be a path prefix for which tests it should apply to (an empty string means it applies to all tests). The noDebug field should be set explicitly if the config should only apply to either Run or Debug, otherwise it will apply to both.

{
	"name": "Run/Debug Tests",
	"type": "dart",
	"request": "launch",
	// Env vars to always be set when running tests
	"env": { "FOO": "BAR" },
  // toolArgs to always be set when running tests
	"toolArgs": ["--platform", "chrome"]

	// path: empty string applies to all tests
	//       "integration_test" only to tests in integration_test folder, etc.
  // This field is required for this configuration to be used by the test runner.
	"templateFor": ""
}

#3863: Tests with < or > in their names will no longer sometimes cause “Couldn’t parse –name” errors when running those tests individually.
#3855: Running all tests should no longer sometimes fail on Windows with “The command line is too long” when there are a large number of test files.
#3849: The Tests: Rerun Last Run command now works for test runs initiated through the Test Runner (note: it does not currently suport runs initiated from CodeLens).
#3699: The dart.suppressTestTimeouts setting will now use package:test’s --ignore-timeouts flag as long as you are using a new enough package:test. This avoids the previous restriction of only working for tests without explicitly defaults and will now apply to all tests.

Other

#3871: @guidezpl improved the ordering of Dart/Flutter’s groups in the VS Code settings editor.
#3903: Running the analysis server with its VM Service enabled (useful for debugging some types analysis server issues) no longer fails to bind to the specified port.
#3874: Following new VS Code guidelines, VS Code’s telemetry opt-out now also applies to the Dart/Flutter extensions. The dart.allowAnalytics has been deprecated/hidden (but if set to false will still suppress analytics). This does not affect analytics sent by the Flutter tool which continue to be controlled by flutter config --[no-]analytics.

Features/Fixes Enabled with Future SDKs

#3873: Code completion for zero-argument functions no longer places the cursor inside the parens.
#3872: The Extract Method code action will now check the extraction is valid before prompting for a method name.
#3869: Some code actions like Surround with if now have improved snippet support and will provide better selections after inserting code.
#3867: Holding ctrl when hovering over paths to examples in Flutter dartdocs will no longer highlight significantly more of the file than included in the path.
#3864: “A request has failed” errors will no longer appear if you navigate to files that reference Flutter colors that are outside of the workspace (such as Flutter SDK sources or Pub package sources).

Experimental

These items also rely on changes to the Dart/Flutter SDKs that have not yet been released to the stable channels, but must also be opted-in to for now. If you’re using pre-release/master versions of Dart/Flutter, please consider enabling these and providing feedback!

#3582/#2059 The dart.enableServerSnippets setting will switch to new context-aware snippets provided by the language server. This should prevent snippets showing up in contexts where they would not be valid (or example stful will not show up inside functions/classes) and will adapt to your language version/lints (for example using final instead of var or using null operators).
#3769: The setting dart.experimentalSdkDaps enables using new DAP implementations that will ship in the Dart/Flutter SDK. These are highly experimental and will only work with the latest development SDKs, but testing and bug reports are welcome.
#3894: The dart.maxCompletionItems setting allows reducing the number of code completion items that will be returned. When the list is truncated, the list will be refreshed as you continue to type. Lowering the value should result in faster completion responses although when typing quickly may briefly show less relevant items as additional items are provided by the language server. The default value is 2000 but will be reduced to something much lower over time (based on feedback).

v3.36.0 2022-03-01

Flutter

#3838: Flutter Apps runs in profile mode will no longer start with paused isolates (which the debugger must unpause) which could make them appear to run more slowly.
#3815: Running an app in Release mode has been simplified with the addition of a new command (Debug: Run App in Release Mode, an automatic launch configuration, and a launch configuration snippet), mirroring the same existing for Profile mode.
#3655: Online devices and offline emulators are now clearly seperated in the device selector.
#3827: stful/stanim snippets no longer generate public API using the private State subclass.
#3843: Icon previews in hovers are no longer missing for newly-added icons or those that start with numbers.
#3821: The “cold boot” emulator options now appear alongside their standard boot counterparts.
#3819: After creating a new project, the prompt shown advising you to press F5 to start no longer notes that a device must be connected.
#3822: Generated debug session names no longer contain tags used to show icons in other parts of the UI.
#3842: Some additional “flutter build” tasks have been added and are now filtered by platform.
#3834: Having quotes around the flutter dependency in pubspec.yaml no longer prevents the project from being detected as a Flutter project.

Debugger

#3840: Errors during evaluation in the watch/variables panels no longer show “function errorString” instead of the actual error message.
#3799: The VM Service URI used by DevTools will now be correctly mapped for use in remote workspaces (for example using VS Code’s Remoting extensions for SSH or Docker).

Commands

#3852: Launching DevTools in an external browser no longer writes an error to the VS Code developer console when using the latest (master) Flutter SDK.
#3817/#3818: @tomgilder contributed a new “Open in Xcode” short-cut for the macos folder in the explorer.
#3813: Using a new version of pub that does not create .packages files will no longer result in additional spurious prompts to fetch packages.

Tasks

#3848: Customizing a Task in a multi-project folder (monorepo) no longer loses the working directory.
#1516: Running tasks automatically upon opening a project (using runOptions in tasks.json) no longer sometimes fails on Windows.
#3847: Running build_runner tasks on the latest stable SDK no longer prints “Deprecated. Use dart run instead.”

Experimental

#3769: A new setting dart.experimentalSdkDaps enables using new DAP implementations that will ship in the Dart/Flutter SDK. These are highly experimental and will only work with the latest development SDKs, but testing and bug reports are welcome.

Features/Fixes Enabled with Future SDKs

#3846: The “Convert Getter to Method” assist now works for extensions.
#3844: Code completion no longer inserts unwanted commas when editing argument names.
#3823: A new “Convert to ‘package:’ import for everywhere in file” fix is available when using the always_use_package_imports lint.
#2492: The “Wrap with Column” refactor is now available when a Widget constructor is selected and not only when there is no selection.
#3830: The “Invalid file path” message sometimes shown when analysis fails will be more specific rather than a catch-all for several types of failure.

v3.34.0 2022-02-01

Testing Improvements

#3791: Tests in nested projects no longer run multiple times when using the Test: Run All Tests command (which often led to package resolution errors as they were running in the context of their parent projects).
#3776: Using the testGoldens function from the from golden_toolkit package will no longer cause issues when trying to run/view the results of tests in the tree. Tests may still appear duplicated in the tree if you are using a version of golden_toolkit that does not include this PR (the fix for that is to upgrade the golden_toolkit package).
#3803/#3705: It’s now possible to override the launch configuration used when running/debugging tests from the test runner. See the Debugger section below for an example.

Debugger

#3759: Clickable paths in stack traces in the Debug Console now jump to the correct line number (instead of always line 1) for assertion failure errors.

#3803/#3802: Creating launch configurations for the standard Run/Debug CodeLens links has been simplified so that it can be done with a single field (and now also applies to executions of tests from the test runner):

  "configurations": [
      {
          "name": "Tests (VM+Chrome, Static Seed)",
          "request": "launch",
          "type": "dart",
          // Set "templateFor" to a path for this config to be used for all
          // Run/Debug links on CodeLens, or running from the test runner.
          // Set to an empty string "" for it to apply to the whole project.
          "templateFor": "test", // everything in test folder
          "args": [
              "-p", "chrome,vm",
              "--test-randomize-ordering-seed=12345",
          ],
          "env": {
              "MY_ENV_VAR": "foo"
          }
      }
  ]

#3749: The customToolReplacesArgs field in launch configurations (used to run custom tools in place of dart or flutter when launching apps) can now be used to replace all tool arguments. However, custom tools must still be compatible with the tool they replace. Replacing/removing the --start-paused argument does not remove the requirement for the custom tool to start the app paused, for example.

Editor

#3804: Class fields are no longer incorrectly colored like methods/functions.
#3788: The dart.triggerSignatureHelpAutomatically setting has been removed in favour of the built-in editor.parameterHints.enabled VS Code setting that does the same.
#3780: Pressing <enter> after starting a triple-quoted string (''' or """) will no longer add unwanted indenting.

Flutter

#3758: Flutter refactor commands in the context menu of Flutter Outline no longer fail on newer SDK versions.
#3767: Trying to use "console": "terminal" or "console": "externalTerminal" in the launch configuration for a Flutter app will now produce a notification that this is not supported (instead of being silently ignored).
#3756: The customTool field for launch configurations is now supported for Flutter apps.

Tasks

#3795: Contributed tasks accessible via the Task: Run Task command can now be run for projects in sub-folders (eg. a monorepo) instead of only at the VS Code “workspace folder” level.
#3801: The Dart: Generate Documentation command now uses the new dart doc command instead of the deprecated dartdoc when using a recent enough SDK.

Pub

#3764: Pub packages fetched by the extension (devtools, webdev) will no longer be reactivated every session if the current latest published version has been retracted.

Docs

#3798: The docs explaining the Dart: Use Recommended Settings command now make it clear that the command is only visible when a Dart project is open.

Features/Fixes Enabled with Future SDKs

#3783: Code completion no longer activates while typing in standard double-slash comments that are immediately before a dartdoc triple-slash comment.
#3778: A new "instance" semantic token modifier has been added to instance members, allowing them to be themed/colored separately to other symbols.
#3770: The Create Method ‘xxx’ fix now includes the required keyword for required named arguments if the library is null-safe.
#3761: Using analysis server plugins such as dart_code_metrics will no longer cause the servers view of a file to become out-of-sync with the editor, resulting in spurious diagnostic errors/warnings being reported.
#3697: The Dart: Sort Members command now correctly moves end-of-line comments along with the code on that line.
#3422: A new lint conditional_uri_does_not_exist allows validating conditional import URIs to ensure they exist.
#1160: Hover tooltips now include the static type of a variable, which may be different to the declared type (for example if the variable is used in an is check).
#3784: Code completion should now include members that can be overridden more reliably.
#3440: New packages added to pubspec.yaml should now be available more reliably after saving and waiting for the *pub get command to complete.
#3438: Fetching packages in a Flutter project should no longer intermittently result in the flutter_gen package failing to resolve.

v3.32.0 2022-01-02

#3729: Pre-release channels are now available for the Dart and Flutter extensions. These channels will replace the manual vsix builds for preview/beta extension releases usually distributed via GitHub. These will usually be published a few times per month prior to stable releases.

If you’d like to help test new versions of the extensions before releases, you can switch to them using the buttons on the extensions pages within VS Code. You can switch back to the Release channel at any time.

While the VS Code marketplace doesn’t support pre-release version numbers, pre-release versions will be in the format x.ODD.YYYYMMDD format while release versions will be in the format x.EVEN.y. Pre-release channel users will always get the latest version of the extension, which may be a release version until a subsequent pre-release version is published after each stable release.

Testing

#3714: The Test: Run All Tests command now works correctly without needing to first open the Testing tab.
#3713: The names of Run All Tests test runs in the Debug Console panel will now use the projects folder name instead of just showing the name of the first file run.
#3712: Tests that are more than 5 levels deep inside your workspace will now be detected as long as they are somewhere within a detected project folder.

Flutter

#3727: The Tests: Run All Tests command no longer fails with “Integration tests and unit tests cannot be run in a single invocation” for projects with both types of tests. Instead, two debug sessions will be spawned - one running all unit tests, and one running all integration tests.

Commands

#3746: Changing project settings while creating a new Flutter project will now be reflected in the UI immediately.
#3735: The Dart: Add Dependency command now trims package names to make it easier to copy/paste from the Pub website.

Debugger

#3741: Long lines printed with dart:developer’s log() function no longer output additional surrounding quotes.
#3715: The Hot Reload and Profiler buttons are now available on the debug toolbar for non-Flutter applications and will run the Dart: Hot Reload or Dart: Open DevTools CPU Profiler commands respectively.

Editor

#3731: Code completion for version numbers in pubspec.yaml will no longer sometimes return incorrect results after modifying the file.
#3728: The Add ‘{package}’ to dependencies fix no longer fails with “Cannot read property ‘replace’ of undefined”.
#742: The .dart_tool folder is now included in VS Code’s watch exclusion list by default.

DevTools

#3750: A new setting dart.updateDevTools has been added that allows disabling auto-updates of DevTools via Pub. This applies only to older SDKs that do not ship with their own bundled version of DevTools.

Features Enabled with Future SDKs

These items rely on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They will show up automatically when you update your SDK in future (or if using development channels depending on the exact version).

#3734: The Create constructor to call super() fix now includes required named parameters as well as positional parameters.

v3.29.0 2021-12-01

Editor

#3682: Code completion now re-triggers automatically after completing an argument name (foo: ).
#3645: Signature help now triggers automatically after completing an invocation that has arguments.
#3620/#3649: Go-to-Definition now uses cached data for improved performance when using the original (non-LSP) language server protocol.

Testing

#3693: toolArgs in a launch configuration are no longer ignored when running a single group/test from CodeLens.
#3687: A new setting dart.suppressTestTimeouts has been added that overrides the default test timeout to avoid timeouts while debugging. In the current form it only applies to tests that don’t explicitly override the timeout but in a future update the setting will use ‘package:test’s upcoming –ignore-timeouts flag to also ignore explicit timeouts.
#3665: For multi-project workspaces, running tests from multiple projects at once now shows the correct test counts instead of only the last projects tests that completed.
#3537/#3673: The legacy test runner (and its associated commands) has been removed from the extension. All functionality should now be available through the built-in VS Code test runner and its own commands.

Debugger

#3685: The dart.vmAdditionalArgs setting and vmAdditionalArgs launch configuration option have been updated to work for both CLI scripts run with dart and tests run with dart test.
#3691: A new setting dart.cliAdditionalArgs has been added to inject args into only Dart CLI script invocations.
#3689: A new setting dart.testAdditionalArgs has been added to inject args into only dart test test invocations.
#3637: A new setting dart.reloadOnSave has been added to suport hot reloading on-save for Dart projects. This is separate to dart.flutterHotReloadOnSave so behaviour can be configured independently and unlike Flutter, it defaults to off for Dart.
#3656: A new launch configuration option customTool allows replacing the tool used when launching debug sessions (dart or flutter). The replacement tools must be compatible with the tools they replace. This may be useful for wrapping dart/flutter with custom behaviour, or running through build_runner. The customToolReplacesArgs option allows the custom tool to also replace the first x arguments from the constructed command.

Flutter

#3647/#3650: @guidezpl added icons against devices in the device picker and status bar based on their types.
#3676: The Flutter: Cancel Widget Inspection now correctly appears in the command palette when in Inspect Widget mode.

Commands

#3635/#3683/#3684: @EhsanAramide contributed support for adding Git and path dependencies via the Dart: Add Dependency command. URLs and paths can be pasted directly into the input box, or you can select the option for path/Git URL for some additional options/a filepicker.

Other

#3698: Running the analysis server with VM Service enabled using the dart.analyzerVmServicePort setting no longer fails when running in LSP mode.
#3608/#3652: @guidezpl grouped all extension settings into categories in the VS Code settings UI.
#3657: A single complete changelog for all versions of the extensions is now available at dartcode.org/releases.

Features Enabled with Future SDKs

These items rely on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They will show up automatically when you update your SDK in future (or if using development channels depending on the exact version).

#3240: Color previews are now shown in more places, including user-defined constant fields. Additionally, the VS Code color picker can now be used to change Flutter colors in source code.

#3646: Flutter widget refactors are now sorted correctly in the Code Actions menu.
#3598: Library-level annotations like @Timeout are now longer sorted (or removed) incorrectly when sorting imports.
#3669: Completions that insert imports automatically will now use relative imports (instead of package: URIs) when the prefer_relative_imports lint is enabled.
#3632: The Dart: Hot Reload command now works when using the (experimental, upcoming) Dart SDK debug adapter.
#3631: A previous fix for Hot Restarting hanging if exceptions occur during the restart has been applied to the (experimental, upcoming) Flutter SDK debug adapter.
#3672: Completing a method/constructor name with no prefix typed no longer inserts parenthesis if they already exist after the cursor.
#2167: Color previews are no longer shown for code that is commented out.

v3.28.0 2021-11-01

Automatic Test Discovery

#3591: It’s no longer required to open or run a test file for tests to be discovered. Test files will be discovered automatically at startup and expanding them will discover the tests within.

Non-Error Test Output

#3606: All output from tests is now recorded in the test history, rather than only error output:

Hot Reload for Dart

#2708: A new command Dart: Hot Reload allows hot reloading in Dart (non-Flutter) programs.

Other Test Runner Improvements

#3595, #3599: The Run Tests button in the VS Code test runner now runs tests more quickly in a single debug session when running full suites (match performance of the legacy Dart: Run All Tests command), even if there are excluded (hidden) test files.
#3597: The Run Tests button in the VS Code test runner is no longer restricted to only tests in the test folder (for example tests in integration_test can be run).
#3605: The locations of dynamic tests in the runner are now kept up-to-date more reliably, so Go-to-Test should no longer sometimes go to the wrong location after modifying the test file.
#3596: Running multiple test files no longer prompts to run for each file if you have unresolved analysis errors.
#3643: The test runner now consistently uses \ for path seperators on Windows.

Flutter Improvements

#3448/#3550: Hot Restart no longer fails to complete if exceptions are hit during the restart.

Editor Improvements

#3633: Angle brackets around type arguments are no longer colored inconsistently for some VS Code themes.
#3589: @Ascenio improved the snippet for a main method to include a return type.
#3640: @rlch contributed a new setting dart.onlyAnalyzeProjectsWithOpenFiles that runs the LSP server in a mode that does not analyze the whole workspace, but only projects for open files. This may improve performance for large workspaces but may limit some functionality.

Other

#3613: The dart.previewLsp setting has been renamed to dart.useLsp. LSP is no longer considered a preview and should be used by everyone. This setting (and support for using the old server protocol) will be removed in an future release so if you believe you have a need to disable LSP, please file an issue on GitHub with details.
#2098: The dart.useKnownChromeOSPorts setting has been removed as it is no longer required to use specific ports on ChromeOS.

Documentation

#3571: The description of the dart.completeFunctionCalls setting has been improved to make it clearer which arguments will have placeholders inserted.

Features Enabled with Future SDKs

These items rely on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They will show up automatically when you update your SDK in future (or if using development channels depending on the exact version).

#3638: Setting dart.onlyAnalyzeProjectsWithOpenFiles should no longer prevent the analysis server from fully initialising.
#3621: The identifier part of an annotation now has a modifier "annotation" so that colors can be customised with "editor.semanticTokenColorCustomizations" (for example to allow matching the colour of the annotations @ tag).
#3618: Class fields now have semantic token type "property" instead of "variable" to match guidelines in the VS Code docs.
#3583: Using the Format Selection command or "editor.formatOnSaveMode": "modifications" to format only modified lines will no longer fail to format the leading indentation of the first line of a range.
#3584: DevTools is now started using the "dart devtools" command instead of "pub global" for new SDKs. This means the version will match what is shipped in the SDK and not what’s published to Pub.

v3.27.2 2021-10-11

#3603: The Dart: Run All Tests command will no longer sometimes add test results to the wrong file in the tree depending on the timing of tests in Flutter projects.

v3.27.1 2021-10-08

#3594: The “Run Tests” button in the VS Code test runner will no longer sometimes only show results for the first suite that ran in the tree.

v3.27.0 2021-10-04

Test Runner Improvements

#3574/#3572: Integration with the new VS Code Test Runner is now enabled by default. Some additional improvements have been made to the integration.

The test tree previously only populated from the file contents when it was first opened, and subsequently only when tests ran. Now the tree updates periodically as the file is modified, including removing tests that have been removed from the file without needing to re-run the whole file or clear the test results.

Dynamic tests (those with variables in their name or using features like Flutter testWidgets variants) are now grouped under a parent node using the name of the test from the editor. As well as being easier to manage, these can now be removed from the tree if the test definition is renamed rather than remaining until you re-run the entire file.

Failed tests will now show their failure message with an expandable Peek window containing the output and history for the test (this requires VS Code 1.61).

Running multiple tests from a gutter icon/tree node are now grouped together by suite so that they run more quickly rather than a seperate debug session per-test.

Flutter

#3580: Running commands like Flutter: New Project in an empty workspace will now correctly initialize the Flutter SDK automatically.
#3564: The colour of the Flutter UI Guides (preview) can now be controlled with the "dart.flutterUiGuides" color in the "workbench.colorCustomizations" setting.
#3585: Flutter UI Guides (preview) are now offset by 2px from VS Code’s indent guides to avoid obscuring them.
#3554: The various Flutter: New XYZ Project commands have been folded together into a single Flutter: New Project command that lists the available templates. Included in this list is the new “skeleton” project template added in Flutter 2.5.0.
#3552: If a platform has been disabled (for example by running flutter config -no-enable-android) the “Enable Android for this project” option in the device manager will now offer to enable it globally before enabling it for the project.

Debugger

#3576: Running Dart scripts with no specific folder open in VS Code has been improved. Instead of requiring a launch.json or the script to be inside a bin, lib or tool folder, loose files will just be run directly when pressing F5 or clicking the Play/Debug icons on the editor title bar.

Editor

#3546: Nested multiline comments will longer cause the following parts of the document to be colored as comments.
#3236: A new setting "dart.normalizeFileCasing" has been added that will normalize all file casing when interacting with the analyzer. This may resolve issues where the the file_names lint still triggers errors because VS Code continues to use the original casing in its API. This setting is disabled by default because there is a small performance hit to hitting the filesystem to find the natural case of a file.

Commands

#3561: The Dart/Flutter: New Project commands now default to the folders last used when invoking these commands.
#3545: All commands/actions that call pub will now use dart pub since the top level pub command is being deprecated.

Docs / website

#3578: Documentation for how to pass --dart-define (Flutter) and --define (Dart) in launch configurations has been updated/improved.

Other

#3577: The "dart.useKnownChromeOSPorts" setting now defaults to false as it should no longer be required. This setting will be removed in a future update so if you find you need to re-enable this, please file an issue on GitHub with details.

Features Enabled with Future SDKs

These features rely on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They will show up automatically when you update your SDK in future (or if using development channels depending on the exact version).

Renaming Files with Classes

#3354: A new setting "dart.renameFilesWithClasses" has been added that allows automatic renaming of files (and updating imports) when classes are renamed if the class/filename match. The allowed options are "never", "prompt" and "always". "never" is the default and disables renaming. "prompt" will ask on each rename, and "always" will rename without prompting.

For the rename to work, the class name and the filename must match (apart from differences in PascalCase for class names and snake_case for files).

New TODO Comments Types

#2364: In addition to TODO, several new comment prefixes are recognised and generate diagnostics - HACK, FIXME and UNDONE. These can be controlled with the analysis_options.yaml file.

Editor Changes

#3555: Code completion will no longer show duplicates if an analysis server plugin is enabled that is interested in Dart files.
#3542: The Assign value to new local variable code action will use final instead or var when the prefer_final_locals lint is enabled.

v3.26.0 2021-09-01

Preview: VS Code Test Runner Integration

#3147/#3538: Initial support for VS Code’s new test runner is available behind the dart.previewVsCodeTestRunner preview setting.

The test runner in VS Code provides consistency across all languages and has some additional functionality that is not possible to build in extensions. In the coming releases the custom test runner in Dart-Code will be removed in favor of the VS Code runner.

The VS Code test runner looks a little different to Dart-Code’s and will persist results across sessions (this means you may see results from the last time you ran a test, even if it was in another VS Code session).

The VS Code test runner also adds new gutter icons showing the last state of a test that can be clicked to run the test (or right-clicked for a context menu).

Many of the existing Dart-Code test commands are available as built-in VS Code test runner commands (and in future, the Dart versions of these commands will be removed).

Improved Version Completion in pubspec.yaml

#2078: Version number completion in pubspec.yaml has been improved. Previously version numbers only showed up if you had previously completed that packages name, but now also show up for all packages that are in the saved version of pubspec.yaml. Versions maybe be annotated with latest or latest compatible to indicate whether there are other package constraints preventing you from using the latest.

These changes require an updated SDK so may not be available yet depending on your SDK channel and also may be unavailable if LSP is disabled (with "dart.previewLsp": false in your VS Code User Settings).

Settings for Flutter: New Project

#1153/#1339: To improve discoverability, settings that affect creating new Flutter projects (such as the Organization name used in bundle identifiers and which languages to use for iOS/Android parts) are now available from a new Settings button when creating the new project. Changes made here will update your VS Code settings automatically, persisting across sessions.

Flutter

#3540: You’ll now be prompted to fetch packages if you open a Flutter project where flutter pub get was last run using a different Flutter SDK to the one you have selected. This will also appear after you switch Flutter SDK using the status bar.

Editor

#3502: Fixes and assists produced by Dart analysis server plugins are now available when using LSP (requires SDK update).
#3270: Several issues that may have contributed to the formatter running endlessly have been addressed (some require an SDK update). If you continue to experience this issue after the next major Dart/Flutter SDK release, please file new issues on GitHub.

DevTools Integration

#3517: tomgilder contributed support for opening external links from embedded DevTools views. This change also requires a related update in DevTools so will not work until that fix is also released and your DevTools has been updated.

Commands

#3501: The “Add Dependency” command now lists packages from the Flutter SDK (like flutter, integration_test, flutter_driver) instead of only packages listed on Pub.

v3.25.1 2021-08-03

#3511: Hot Reload no longer stops working after a Hot Restart.

v3.25.0 2021-08-02

Improved Dependency Management

#3306/#3474: Two new commands Dart: Add Dependency and Dart: Add Dev Dependency have been added to simplify adding new dependencies to your puspec.yaml. The commands will provide a type-to-filter list of packages periodically fetched from Pub.

The commands are also available from context menus and the title menu in the dependencies tree.

The commands can also be invoked as quick-fixes on unresolved import 'package:' statements.

#3500: Finally, direct and dev dependencies can be removed directly from the context menu in the dependencies tree.

Note: Some of these features rely on an update to the pub deps command so may not be visible until a future SDK update depending on your SDK channel.

Fix All Command

#3445/#3469: The “Fix All” command is now available for Dart files and can fix all of the same issues as dart fix for the current open file in one step.

This can also be set to run on-save by adding "source.fixAll" to the "editor.codeActionsOnSave" VS Code setting.

Note: This feature relies on changes in the Dart SDK so may not be visible until a future SDK update depending on your SDK channel. It is also only available when running in LSP mode (so you must not have set "dart.previewLsp": false in your VS Code settings).

Flutter

#3498: The root widget of your Flutter app should no longer build multiple times on first startup when launching in debug mode from VS Code.
#3482: When using the variant parameter of testWidgets, you should no longer recieve “No tests match regular expression…” errors when trying to run using CodeLens (requires SDK update).
#3441: @Semvrij contributed support for color previews in the editor for the css_colors package.
#3483: @Semvrij contributed a fix for missing color previews when using an uppercase X in hex values for the Color constructor.
#3487: The “Toggle Platform” command has been replaced with “Override Platform” and now allow selecting the platform to emulate rather than only toggling between Android and iOS.
#3465: Flutter web apps should no longer sometimes start up showing just a white page.
#3454/#3463: Flutter apps should once again respond to changes in your system theme (when not overridden using the Flutter: Toggle Brightness command) rather than being locked to the theme applied when the debugger connected.
#3477: The DevTools inspector button on the debug toolbar should once again appear in debug mode.

Editor

#3442: Links to error documentation are now available from the Problems tag when using LSP.
#3124: Some settings like dart.lineLength now work at the workspace-folder level instead of only at the workspace level when using LSP (requires SDK update).
#542: “Convert getter to method” and “Convert method to getter” refactors are now available when using LSP (requires SDK update).
#2056: Syntax highlighting is now more reliably for interpolated strings that contain additional braces and quotes inside their expressions.

Other

#3481: @iChenLei migrated the extensions tests from the deprecated vscode-test NPM package to @vscode/test-electron.

v3.24.2 2021-07-05

#3462: Using args in a flutter test launch configuration no longer fails to run with an error.

v3.24.1 2021-07-04

#3459: Fixed handling of dart.flutterTestAdditionalArgs setting.

v3.24.0 2021-07-01

Dependencies View

#3095: The dependencies view now has tooltips that show the shortest path from your package to a transitive dependency to help you understand where it comes from.

Note: This feature relies on an update to the pub deps command so may not be immediately visible depending on your SDK channel.

Launch Configurations

#3414: The explorer context menu now includes a command to quickly create a launch configuration in launch.json for a script and open it for editing. This makes it easier to switch between launching different files at the top of the Debug side bar.

Debugger

#3426: Flutter debug toggles like Toggle Debug Painting are now correctly restored after a hot restart.
#3434: The "console" field in launch.json that controls where Dart CLI scripts run now accepts an additional value "externalTerminal" that will spawn the script in an external terminal rather than using VS Code’s integrated terminal.
#3431: Using the "args" field in launch.json for an attach request no longer reports that the field is invalid.

Flutter

#3423: The Enable {platform} actions in the Flutter device selector now enable only the selected platform rather than all available platforms.
#3410: A notification is now shown if the Flutter device daemon terminates during startup (for example if the dart.flutterAdditionalArgs setting contains arguments not valid for flutter daemon).
#3366/#3381: @Hamdor contributed showing an option to cold boot Android emulators in the Flutter device selector.
#3364: Colors using the Color.fromRGBO constructor now show color previews in the

Editor

#3412: Method calls on unresolved/invalid variables are consistently uncolored (requires SDK update).
#3407: The “ignore {lint}” quick-fix now correctly appends to existing ignore comments instead of inserting new ones that would prevent the original ignores from working (requires SDK update).
#3395: Conditional imports are now syntax highlighted.
#3385: Code completion now automatically triggers when completing the import ''; snippet or selecting a folder when using LSP (requires SDK update).
#3374: The name part of named constructors are now coloured the same as methods (instead of classes) when using LSP (requires SDK update).
#3357: Hover tooltips now format method/function signatures over multiple lines as if formatted with trailing commas (requires SDK update).
#3335: A new “ignore {lint} for file” quick-fix allows ignoring a lint for an entire file in one go (requires SDK update).
#3308: The void keyword now has a semantic token modifier to allow its color to be customized differently to other keywords (requires SDK update).
#3269: An export directive that references a non-existent file now has a quick-fix to create the file (requires SDK update).
#3268: The quick-fix to create files from a part directive now prefills the library filename in the created file (requires SDK update).
#3259: The error message reported when failing to resolve includes in an analysis_options.yaml file now includes information about the project being used to resolve the package URI (requires SDK update).
#3071: Go-to-Definition on a conditionally imported filename now jumps directly to the file instead of showing a picker of all files in the directive (requires SDK update).
#2834: Invoking Signature Help/Parameter Hints in type arguments now shows the type parameters and their constraints (requires SDK update).
#1808: Status bar entries added by the Dart extension can now be individually shown/hidden using the context menu.
#1619: A new command Toggle Dartdoc Comment is available for key-binding that will toggle triple-slashes /// for the current selection (similar to the existing Toggle Line Comment command but with an extra slash).

Docs

#3367: The FAQ entry on SDK location now details more places that the extension searches for SDKs.

v3.23.1 2021-06-17

#3413: Opening the DevTools Performance page no longer shows “The performace screen is not available for this application” for some versions of Flutter.

v3.23.0 2021-06-01

Profile Mode Improvements

#765: Running your Flutter app in Profile mode has been made simpler:

Profile CodeLens

A new Profile CodeLens shows against the main function in a Flutter app. Clicking this will run your app in profile mode and also automatically launch the DevTools performance page.

Debug: Profile Flutter App Command

A new command has been added that also runs your app in profile mode and automatically launches the DevTools performance page.

Launch.json Configuration Snippet

A snippet has been added to quickly add a profile mode configuration to your launch.json. This should be used if you need to customise arguments or environment variables for your app. You can also use a launch configuration to replace the built-in Profile CodeLens link (see issue #3311 noted below).

Additionally:

Creating a new launch.json using the create a launch.json file link in the Run side bar will now include both a debug and profile configuration.
The automatic debug configurations accessible from the show all automatic debug configurations link on the run side bar and through the Debug: Select and Start Debugging command now also include a Flutter Profile Mode option.

Improved Dependencies Tree

#3202: The dependencies tree is now split into seperate folders for direct, dev and transitive dependencies (this relies on SDK changes that have not yet reached the stable channel so may not appear immediately).

DevTools Integration

#3365: DevTools windows will now inherit the font size set in VS Code’s editor.fontSize (requires DevTools update).

Editor

#3332: LSP now has support for the Expand Selection command and will expand to method and constructor invocations (requires SDK update).
#3329: LSP now correctly highlights escape characters in strings (requires SDK update).
#3318: Syntax highlighting for complex expressions in interpolated strings has been improved when using LSP (requires SDK update).
#3297/#1201: Parameter lists that span multiple lines can now be folded (requires SDK update).
#2937: Quick-fixes that create constructors now honor the sort_constructors_first lint when picking where to insert the new constructor (requires SDK update).
#1890: A new “Wrap with builder” code action has been added that works like “Wrap with widget” (requires SDK update).
#3340: Workspaces that contain virtual folders (such as LiveShare) are now able to load the Dart extension. This restores previous behaviour that was disabled by a VS Code update requiring extensions to explicitly opt-in to this behaviour.

Debugger

#3338: The “Starting debug session” toast notifications should no longer stay around after the app starts when running in profile/release modes.
#3326: Error text in the debug console no longer uses custom colours that could result in low contrast when using custom themes with some background colors.
#3311: Custom CodeLens links can now replace the built-in Run/Debug/Profile links by using "Run", "Debug", "Profile" or "${debugType}" as their titles.
#3169: A new setting dart.cliConsole allows setting the default console (debugConsole or terminal) for Dart CLI apps.
#3353: Launch configurations can now use the serviceInfoFile field for Flutter applications to aid attaching to apps spawned by custom embedders.
#3358: Restarting the debug session for a Dart CLI script no longer results in the “Terminating debug session” toast notification staying around.

Flutter

#3315: A new setting dart.flutterShowEmulators controls whether emulators are hidden from the device selector in remote workspaces. This may be useful if your remote workspace is a local container and you can interact with emulator processes spawned inside it.
#3352: @Delgan contributed updating the Launch Emulator command to also take the dart.flutterShowEmulators setting into account.
#3347: The stful, stless and stanim Flutter snippets have been updated to assume null-safety and no longer generate warnings when used in projects created with the latest stable Flutter SDK.
#3343: The “Convert to StatefulWidget” code action no longer adds an additional underscore if the class already contains one (requires SDK update).
#3376: Icons previews now work for many new Icons added to Flutter.

Other

#3361: The dependencies tree will no longer highlight project folders in red if the project has errors.
#3304: The Dart extension now only activates at workspace-open if a pubspec/Dart file is found in the top 3 levels. Previously a full workspace search would be done which could be slow and would often trigger a 7 second timeout in VS Code which caused it to pre-emptively activate. This could result in the Dart extension running for large non-Dart workspaces. If your workspace does not have a Dart file within the top 3 levels the extension will still activate if you open a Dart file further down the tree.
#3348: Adding additional folders to the workspace with File -> Add Folder to Workspace will no longer generate errors in the console when using LSP.

v3.22.0 2021-05-03

Flutter Integration Testing

#3009/#3133: Flutter tests inside an integration_test folder are now recognised as tests and run on the selected device. See flutter.dev/docs/testing/integration-tests for more information on using the Flutter SDK’s package:integration_test.

New Refactors

#547/#545: New refactors have been added for Inline Method and Inline Local Variable (requires SDK update).

Editor

Items here marked “(requires SDK update)” also rely on changes in the Dart/Flutter SDKs so may not be immediately visible depending on your Dart/Flutter SDK channel.

#3303: When using LSP and the completeFunctionCalls setting, code completion will no longer insert additional parenthesis/argument placeholders when they already exist in the document (requires SDK update).
#3289: Brackets around references in dartdoc comments are no longer colored inconsistently when using LSP with Semantic Tokens (requires SDK update).
#3281: Code completion no longer incorrectly returns results when invoked in a comment right at the end of a file.
#3253/#3250: Renaming files that do not need to update any import statements will no longer trigger the VS Code refactor prompt (requires SDK update for LSP, not for non-LSP).
#3227: Code completion no longer shows duplicate classes when multple libraries are imported that re-export the same symbols (requires SDK update).
#3225: Code folding now works for Enum bodies (requires SDK update).
#3211: Code completion now intelligently triggers automatically for LSP when typing imports/slashes/interpolation(requires SDK update).
#3248: A new setting dart.automaticCommentSlashes has been added to control the new automatic comment marker behaviour added in the previous release.
#3174: Code completion now includes ? in the display of nullable types in signatures and descriptions.

Flutter

#3302: Custom emulators (using flutterCustomEmulators) now show error messages if they fail to launch.
#3267: Custom emulators (using flutterCustomEmulators) can now define additional environment variables using the env key.
#3258: Automatic Flutter initialization now works even if you have no other Dart SDKs on PATH.
#3246: When using embedded DevTools, dart.openDevTools will now open the embedded Inspector page for Flutter apps instead of opening a separate browser. For non-Flutter apps, DevTools will still be launched in a browser.

Debugger

#3294: Custom CodeLens templates can now use exact file paths in their path filter instead of only folders.

Commands

#3275: Embedded DevTools is now disabled for IDEs like Theia that do not support iframed webviews.
#3274: Embedded DevTools are now supported for Remote VS Code sessions where the necessary ports can be forwarded.
#3261: VS Code shortcut keys (like the command palette) now work even when embedded DevTools has focus (requires DevTools update).

Other

#3301: The experimental flutterDisableVmServiceExperimental setting has been removed.
#2853/#3292: Snap support has been simplified and should now work more reliably if you have never run flutter since installing the Snap package.
#3257: The New Project commands now spawn in the current window instead of opening new windows.
#3256: LSP will no longer be enabled by default for editor versions that do not meet the minimum required version for the LSP client.
#3183: Settings that are considered experimental (and may have significant issues) are now more clearly marked in their descriptions.
#3300: Enum settings now have improved descriptions for their values when using the VS Code settings UI.

v3.21.1 2021-03-31

#3245: A bug in the change for #3203 that caused only double-slashes // to be included after a triple-slash /// comment has been fixed.

v3.21.0 2021-03-31

Editor

Many of these editor changes rely on changes in the Dart/Flutter SDKs so may not be immediately visible depending on your Dart/Flutter SDK channel.

#3143/#3215: The “Wrap with widget” action now correctly pre-selects the text “widget” when LSP is enabled.
#3214: LSP code actions that insert multiline text using “snippets” now indent correctly.
#3203: Pressing <enter> on a comment line (starting with //) now auto-inserts // on the next line, matching the existing behaviour for triple-slash /// comments.
#3177: The dart.autoImportCompletions setting is now supported by LSP, allowing auto-import completions to be disabled.
#3159: Renaming a variable to match the name of a constructor called in the same scope no longer returns a confusing error message about shadowing variables.
#3170: Code completion no longer incorrectly triggers in comments at very end of a file.
#3160: Code completion no longer sometimes returns stale results based on the version of a file first opened in the session.
#2873: The performance of Ctrl+Clicking symbols when LSP is enabled has been improved.
#101: Code completion is now able to suggest package names in the dependencies and dev_dependencies sections of pubspec.yaml.

Commands

#3216: New commands Pub: Upgrade Packages –major-versions and Flutter: Upgrade Packages –major-versions will upgrade packages using Pub’s --major-versions flag that updates constraints in pubspec.yaml.
#3213: Output panes no longer disappear then reappear (causing a visible flicker) when running new commands.
#3212: The Flutter: Screenshot command works again with the latest versions of Flutter.
#3237: Clicking the Get Packages button in the editors menu bar for a Dart project’s pubspec.yaml in a workspace that also contains a Flutter project will no longer run flutter pub get instead of pub get.
#3179/#3238: The Dart: New Project command now uses dart create instead of Stagehand for Dart SDK versions >= v2.10.0.

Testing

#3151/#3157: The Run Skipped commands/buttons added in the previous version now also work for Flutter tests when using a new enough Flutter SDK (this does not include stable at the time of the release).
#3098: Test Discovery no longer sometimes inserts additional unknown test nodes into the tree if you open the test file immediately after starting a test run.

Debugger

#3224: Fields now correctly show in debug tooltips when evaluateGettersInDebugViews is set to false (only getters are excluded).
#3210: Widgets in local (path) packages are now shown correctly in the DevTools inspector summary tree.
#3198: The DevTools server address is no longer passed multiple times with --devtools-server-address when launching Flutter apps.
#3195: Attaching to Dart or Flutter apps now correctly shows the stdout stream in the Debug Console.
#3188: The editors run/debug title buttons have been moved to the new VS Code editor/title/run menu, allowing them to appear before other buttons and overflow better.
#3187: Frames that cannot be restarted from (the top frame, and frames after an async boundary) now show the button disabled instead of reporting an error if clicked.

Flutter

#3196: Flutter gutter icons now work for expressions that use conditionals expr ? widget1 : widget2.
#3217: A new setting dart.flutterShowWebServerDevice allows enabling the web-server device even when running locally. Using the web-server device requires the Dart Debug extension and the Chrome device is still the recommended way for non-remote development.

v3.20.1 2021-03-03

#3173: LSP Support is now enabled by default for some users. This will be extended over coming releases to include all users though can be opted-out by explicitly setting the dart.previewLsp setting to false.

v3.20.0 2021-03-01

Testing

#3048/#3131: The ability to run Skipped tests (--run-skipped) has been added to the test runner toolbar and context menus. This is currently only supported for Dart projects but will be enabled for Flutter projects in a future version. This allows a tests to be run even if they are annotated with skip: true to check their status without needing to modify the code.

#3097: Additionally, running a specific test from CodeLens links will always pass --run-skipped when supported, making it easy to run skipped tests directly from the editor.

Other test runner changes include:

#3156: Test suite/group nodes overall status now only shows as Skipped if the whole group is skipped (if a group has a mix of pass/skip the overall status will show as Passed).
#3146: Viewing test output from the last run of a test has been moved to the context menu rather than automatically opening when clicking on a test in the tree (this caused some confusion due to switching from the Debug Console to a pseudo terminal).
#3119: Newlines in test/group names are now removed to show more of the name in the test tree node.
#3154: Test output is now cleared on each new run, so only output from the last is shown.

Flutter

#3110/#3122: The hot-reload-on-save setting now has an additional option to reload on all saves (including auto-saves) as well as just manual saves.

#3118/#3123: The hotReloadProgress no longer (incorrectly) applies to build progress. Build progress will once again show as notifications regardless of this setting.
#3149: When Flutter needs initializing at project load (for example after an SDK update), a different Dart SDK version (for example from PATH) will no longer be selected instead of the one provided by the Flutter SDK.

Editor

Items here marked “(requires SDK update)” rely on changes in the Dart/Flutter SDKs so may not be immediately visible depending on your Dart/Flutter SDK channel.

#3141: The Create file quick-fix on imports no longer fails to create files when using LSP (requires SDK update).
#3104: New imports inserted by fixes or code completion will no longer be inserted above file-wide annotations such as @TestOn() (requires SDK update).
#3103: The Extract Method and Extract Widget refactors now prompt for names when using LSP.
#3074: Changes made to generated Flutter localizations (in the synthetic l10n_gen package) are now detected by the analyzer without a restart (requires SDK update).
#2998: Code completion now supports “insert mode” (Shift+Enter) when using LSP (requires SDK update).
#2854: The warning “Code actions of kind ‘quickfix ‘requested but returned code action is of kind ‘refactor.extract’.” is no longer shown in the console when key-binding specific fixes.
#584: Refactors/fixes that insert multiline code generate correct indentation when using LSP.
#2816: Renaming a named constructor no longer adds an additional dot in Dartdoc comments, breaking the reference to the constructor (requires SDK update).
#3161: When using LSP with semantic tokens, the @ of annotations are now coloured the same as variables by default.

Debugger

#3167: Launching non-Flutter web apps no longer fails with an error about “devtools-server-address” if DevTools has been started for the current session.

Commands

#3162: The current DevTools version is now shown in a tooltip when hovering over DevTools in the status bar.
#3158: The Dart: Reanalyze Project and Open Diagnostic Server commands no longer fail when using LSP.
#3145: The Flutter: Run Flutter Doctor command no longer reports a spurious error if Flutter failed to initialize at startup.
#3138: Activating global Pub packages like devtools and webdev will no longer report failures if the latest published stable version is not compatible with your current SDK.

Other

#3142: DevTools is no longer eagerly/background-activated for non-Flutter workspaces.
#3120: New releases of DevTools are now detected and installed even when DevTools is eagerly/background activated.
#3135: Failing to send analytics no longer reports an error and disables sending analytics for that whole session.

v3.19.2 2021-02-06

#3125: Windows users should no longer see spurious “Your Dart SDK has been updated” messages, believed to have been caused by the SDK’s version file being accessed and not modified.

v3.19.1 2021-01-29

Test Runner

#3060/#3100: The Run/Debug Failed context menu items are now available on group nodes in the test tree in addition to suite notes.
#3093: Test suites should no longer be re-sorted during runs causing them to move around. If their status changes to failed, they will still be promoted to the top.
#3058: The “Run All Tests” command now correctly removes stale tests after completing (for example, tests that had been renamed).
#3052: Test Discovery should no longer result in duplicate nodes in the test tree on Windows.
#3038: Skipped tests can now be hidden from the test tree.
#3049/#3053: A new command Clear Test Results removes all test results from the test tree until they are next run/discovered.
#3050/#3084: New toolbar buttons and a menu have been added to the top of the test tree for running tests, clearing test results and for toggling visibility of hidden tests.
#3094: Test icons have been (slightly) updated.

LSP Semantic Tokens

#2202: LSP’s Semantic Tokens are now supported by Dart Code. In order to use semantic tokens you need:

Dart Code v3.19.0 or later
To have the LSP Preview enabled (see the dart.previewLsp setting)
A Dart SDK v2.12 or later or a Flutter SDK containing the same (these changes are not in the stable channels at the time of the Dart Code release)

Semantic tokens fix a number of inconsistencies in syntax highlighting that were not easily addressed using the original textmate grammar. Below is a screenshot comparing the original colouring (left) and new colouring (right).

Some specific issues this addresses:

#2241: Allow highlighting unknown/invalid types differently to known types.
#2237: Allow variables to be themed.
#1900: Allow changing the color of named parameter labels in themes.
#1688: Allow coloring different types of variables/fields differently in themes.
#311: Variable names starting with uppercase characters should not be coloured as types.
#2748: Methods named get or set are incorrectly colored as keywords.

LSP Improvements

Items here and in subsequent sections marked “(requires SDK update)” rely on changes in the Dart/Flutter SDKs so may not be immediately visible depending on your Dart/Flutter SDK channel (these changes are not in the stable channels at the time of the Dart Code release).

#2761: Imports are now updated when moving/renaming files when using LSP. This is currently only supported for single-file moves/renames (requires SDK update).
#3081: Flutter gutter icon previews no longer sometimes fail to render the first time you open a file.
#3079: Flutter UI Guides no longer sometimes fail to render the first time you open a file.
#2951: The “Extract Local Variable” refactor is now available for LSP (requires SDK update).
#2653: Holding Cmd/Ctrl when hovering over a symbol will now show the correct code preview in the hover popup.
#2896: Flutter icon previews now show up in completion and hovers for LSP.

Flutter

#3045: The Enable <platform> entries in the device picker now show up for platforms for which there are available emulators, even if there are no active devices. For example, Enable Android will show up if your current project is missing its Android folder/dependencies if you have Android emulators, even if you have no active Android devices.
#3034: On Flutter’s first run, when the Initializing Flutter… notification appears, output will be streamed to the output window to make it clearer what’s happening and/or why it’s taking a long time.
#3022: Platform-specific options are now hidden when that platform is disabled, for example with flutter config --no-enable-android (requires Flutter SDK update).
#3020: If the Flutter SDK’s version file changes while the analyzer is running, you’ll now be prompted to restart it using the new SDK version.

Editor

#2973: Code completion will no longer sometimes stop returning most results after running a Flutter app on Windows (requires SDK update).
#3067: Cupertino icon previews now show in code completion/hovers in addition to Material icons.
#3066: Icon variants (such as outlined, rounded) now correctly render previews.
#3030: Multi-line TODO comments are now supported when subsequent lines are indented by an extra space (requires SDK update).
#2800: Comments that span multiple lines can now be collapsed using code folding (requires SDK update).
#2982: Code completion no longer fails to suggest type names after the word static in class field definitions (requires SDK update).

DevTools Integration

#3064: DevTools can now be started without an active debug session, allowing you to connect to an application not launched from VS Code.
#3063: The Open DevTools command is now listed in the Flutter category in addition to Dart.

The following items rely on changes in the Flutter SDK and DevTools so may not be immediately visible depending on your Flutter SDK channel (these changes are not in the stable channels at the time of the Dart Code release).

#3086: VS Code now shares its DevTools instance with Flutter to support deep linking.
#3088/#3087: Some types of Flutter widget errors (initially render overflow errors) will trigger warning notifications including a quick way to inspect the erroring widget.

Debugger

#3033: Hot-reload-on-save no longer fires for Save events triggered by VS Code’s auto-save feature. Pressing Save manually will still trigger a reload even if there are no unsaved changes.
#2974: The debuggers request for the top stack frame is now satisfied using the VM pauseEvent’s topFrame, reducing latency when the debugger breaks; this is a performance optimisation that mostly affects web.

Documentation

#3046: @kagouda updated references to the Flutter: New Project command in docs to the new name Flutter: New Application Project.
#2824: The build_runner tasks have been added to the Tasks page with a link to build_runner documentation.

v3.18.1 2021-01-07

#3029/#3051: URLs used to spawn DevTools have been updated to support the upcoming release that renames Timeline to Performance and Performance to CPU Profiling.

v3.18.0 2020-12-24

LSP Improvements

Several improvements have been made when running with the LSP Preview. Many of these rely on changes in the Dart language server so may not be immediately available depending on the Dart/Flutter channel you are using. At the time of writing, they have not yet reached the Flutter stable channel.

#3010: TODO comments now show in the problems list if dart.showTodos is true.
#2808: Placeholders for parameters marked with the required keyword are now inserted when completing a function/method when dart.completeFunctionCalls is enabled.
#1960: Placeholders for parameters marked with the @required annotation are now inserted when completing a function/method when dart.completeFunctionCalls is enabled.
#3006: Selecting setState from completion no longer inserts two function placeholders.
#2992: Completions for some auto-import functions no longer fail to include parens/arguments when dart.completeFunctionCalls is enabled.
#2975: Code completion no longer inserts unnecessary tabstops for some functions that could prevent code completion from working if editor.suggest.snippetsPreventQuickSuggestions has not been disabled.

Flutter

#3016/#3026: New settings dart.flutterRunAdditionalArgs and dart.flutterAttachAdditionalArgs have been added that behave like dart.flutterTestAdditionalArgs but injecting args into flutter run and flutter attach commands run by the debugger respectively.
#2999/#3000: A new setting dart.flutterWebRenderer allows easily setting Flutter’s web renderer at the global (User Settings) level or per-workspace.
#2963/#3004: New commands have been added to create module, plugin and package Flutter projects. The original Flutter: New Project command is now named Flutter: New Application Project to avoid ambiguity.

Editor

#2984/#2991: The “Dart from Flutter” label no longer shows in the status bar when the active file is HTML.
#2575: Syntax highlighting no longer colors unicode characters following a variable/expression as part of the variable.

Commands

#3013/#3014: Folders inside .dart_tool that contain pubspec.yaml files will no longer show up in the project list.
#2989/#2994: The New Project commands now allow selecting a folder before entering a name and will pre-populate the name with a placeholder that does not already exist on disk.

Testing

#2832: A warning will now be shown when running individual tests using CodeLens if multiple tests are run (as a result of having multiple tests with the same name).

v3.17.1 2020-12-10

#3001: Using bleeding-edge analysis server code built with v3.16 of the LSP spec no longer reports “Invalid params for initialize: params.capabilities.textDocument.rename.prepareSupportDefaultBehavior must be of type PrepareSupportDefaultBehavior”.

v3.17.0 2020-12-04

LSP Improvements

Many enhancements have been made when running with the LSP Preview. Many of these rely on changes in the Dart language server so may not be immediately available depending on the Dart/Flutter channel you are using. At the time of writing, they have not yet reached the Flutter stable channel.

[LSP] Apply-all Fixes

#2926: Some quick-fixes are now able to be fixed for the entire file in one go.

[LSP] Complete Function Calls

#2823: A new setting dart.completeFunctionCalls will cause code completion on functions/methods to include parentheses and argument placeholders for required arguments.

[LSP] Format Selection

#812/#2790: It’s now possible to format only a selection of code (or also only lines modified according to source control).

[LSP] `pubspec.yaml` and `analysis_options.yaml` Code Completion

#114/#2110: Basic code completion is now available for pubspec.yaml and analysis_options.yaml files. This includes static identifiers and also lint names. It does not include Pub package names.

Editor

#1626: Formatting files over 100k in size will no longer result in selections and breakpoints losing their positions.
#1590: The Dependencies tree now starts from package roots rather than the lib folder, simplifying opening files outside of the lib in dependencies.
#2964: The dart.analysisExcludedFolders setting is now also used to exclude projects from project detection and project selection inputs. This means an excluded Flutter project will not force a workspace into using a Flutter SDK if all other projects are only Dart.
#2740: A new command Dart: Linkify Selected Text will print the selected text to the terminal with package: links/filenames linkified. This is useful if you have a text stack trace (eg. in a log file) that you’d like to quickly linkify to be able to navigate.
#2960: [LSP] Duplicate code actions no longer appear in the lightbulb menu when two diagnostics have similar fixes on the same line.
#2945: [LSP] Enum members now use the EnumMember SymbolKind.
#2653: [LSP] The range of code shown when holding Cmd/Ctrl while hovering a symbol should now more accurately reflect the actual code range.

Flutter

#2723/#2718: VS Code tasks are now contributed for additional commands like flutter install and flutter build and can be customized by copying to tasks.json using the Cog icon in the Tasks: Run Task picker.
#2958: The error shown when Flutter fails to initialize now includes a Show Log button.
#2929/#2935: The dart.flutterAndroidX setting has been removed. This support has been enabled by default for some time.

Debugger

#2933: Debugger stack traces are now fetched in batches of 20 frames to improve performance.
#2970/#2971: A new setting dart.hotReloadProgress controls whether Hot Reload and Hot Restart progress is reported in the status bar or as a large notification (defaults to notification).
#2950/#2956: Dart tests will be run with dart run test:test when using a Dart SDK >= v2.12.
#2910: Large stack traces in the debug console are no longer excluded from linkifying.
#2783/#2954: Debug Adapters now require fewer variables be passed to launchRequest, simplifying their use by other editors.

Testing

#2934: The Test tree should no longer show duplicate nodes after running tests many times concurrently.
#2915/#2916: @bencehornak contributed a new dart.flutterTestAdditionalArgs setting that allows injecting arguments to call invocations of flutter test (eg. to always run with --coverage).

Commands

#2944: Fetching packages now uses dart pub get instead of pub get for Dart SDKs >= 2.12.
#2931: DevTools can now be opened in an external browser from the status bar even if it is already open in an embedded view.

Other

#2930: @timsneath Contributed improved descriptions for all settings and added links to docs where appropriate.
#2917: The extension no longer fails to activate if there are folders in your workspace that cannot be read due to permissions errors.
#2919: Dart-Code extension code is no longer minified, improving the locations reported in unhandled errors in its own code.
#2928: “MaxListenersExceededWarning: Possible EventEmitter memory leak detected” leak no longer occurs after multiple silent extension restarts.
#2927: “Cannot read property ‘dispose’ of undefined” no longer occurs when reloading after an SDK-not-found error.

Tasks

#2923: build_runner tasks now work reliably if run from the recent tasks list.
#2921: The previewBuildRunnerTasks preview flag has been removed and build_runner tasks are now always available..
#1284: Errors from build_runner tasks are now handled more reliably and will produce diagnostics in the Problems pane.

v3.16.0 2020-10-30

Language Server Protocol Preview

In an upcoming release Dart-Code will switch to using the Language Server Protocol for communicating with the Dart language server. Please consider enabling this now to help find any remaining issues before the switch.

Testing Improvements

#2357/#2828: A new command has been added to allow re-running all failed tests.

This is also available on the context menu for individual test suites.

#2826/#2892: Opening a test file will now automatically discover available tests without having to first run them. This functionality only works when using LSP (see above) and can only discover groups/tests with static names (without interpolated variables).

#2825: Clicking on a Test node now shows the test output in a pseudo-terminal window instead of an output pane, allowing file/package paths to be linkified.
#2835: The test tree should now scroll to the first test failure in a test session more reliably.
#2840: Running tests that have interpolated string names from CodeLens when using LSP no longer fail with an error.

Editor

#2885: The Refactor context menu is now available when using LSP.
#2857: Color previews in the gutter are now more reliably constrained to known Flutter color classes.
#2500: Hovering over an error sends repeated requests for quick fixes.
#2899: The “Dart Analyzer has terminated” messages will now appear immediately upon the server terminating rather than only on the next interaction with the server.
#2898: The “Dart Analyzer has terminated” message now works when using LSP instead of failing silently.
#2897: The “Dart Analyzer has terminated” message will no longer flash/re-appear on every interaction with the server (for example while typing) and will remain visible after clicking the “Show Log” button.

The following fixes apply when using LSP and require an updated Dart SDK so may not be immediately available unless you’re using a dev/master release of the SDK.

#2745: Refactors that would generate invalid code (for example renaming a variable to become private that is used outside of its library) will now show a confirmation allowing you to proceed rather than immediately aborting.
#2125/#2693: A new setting dart.previewCommitCharacters enables ( as a code-completion commit character, allowing you to use ( to both accept the selected completion item and also insert the parens.

Flutter

#2239/#2870: Flutter UI Guidelines will no longer appear tilted around multiline comments when using some specific combinations of fonts and VS Code themes.
#2886/#2891: The default location for installing the Flutter SDK using Snap on Arch Linux is now included in default search paths.
#2856: The “Initializing Flutter” step seen after first installing/upgrading Flutter now correctly logs to captured log files to help diagnose issues if it fails.
#2842: An experimental launch.json field (flutterDisableVmServiceExperimental) has been added that allows launching Flutter apps without a direct connection to the VM Service. This may help in some remote scenarios (such as some cloude IDEs) to allow basic launching of apps without debugging where proxies prevent a connection to the VM service.

The following fix requires an updated Flutter SDK so may not be immediately available unless you’re using a dev/master release of the SDK.

#2844: The “Start iOS Simulator” option is no longer missing from the device selector when an Android SDK is not installed.

Terminal

#2858: The terminal link provider now detects line/column numbers that are seperated from the path by a space.

Debugger

#2597: Larger build/hot reload notifications have returned! 🎉
#2855: Variables/watch/evaluations no longer fail with “The method ‘-‘ was called on null” when debugging web projects.

Other

#2789/#2875: Additional Dart: Capture Logs commands have been added that automatically select which categories to log (for example Capture Analysis Server Logs) to simplify collecting the right information when reporting issues.
#2872/#2876: Log files created with the Dart: Capture Logs commands now include which log categories are being recorded.
#2836/#2889: A new setting dart.showDevToolsDebugToolBarButtons allows toggling DevTools buttons on the debug toolbar.
#2841: Several tweaks have been made to improve compatibility with Theia-based cloud IDEs that do not implement the full VS Code API surface.
#2912: Starting with this version, both Dart and Flutter extensions are being published to open-vsix.org for easier use by non-VS Code editors.

v3.15.1 2020-10-15

#2877: Large strings printed to the console while debugging will no longer consume significant amounts of CPU in the debug adapter.
#2880: Stack frames printed to the debug console with no line/column information will no longer result in the URI/filename disappearing.

v3.15.0 2020-09-30

Terminal

#2099/#2581/#2817: package: links are now detected in the built-in terminal and automatically linked as long as they are referenced by one of your projects.

Stack Trace Improvements

#2795/#2796: Relative paths and dart: libraries are now detected in stack traces printed to the debug console.
#2794: Stack traces printed to the debug console while running tests are now detected and linked.

Flutter

#2793/#2809: Errors for required parameters (like “vsync is not detected as a named parameter”) should no longer appear after using the Flutter: New Project command.
#2776: Icons previews have been updated to support new rounded/outline variants and many new Cupterino icons.

Editor

#2813: Code-fixes that include suggestion drop-downs will no longer generate incorrect code when one of the suggestions contains a comma.

The following changes include changes in the SDK and therefore may only apply when you are using a new enough SDK version. Those marked LSP may only apply when using the LSP preview ("dart.previewLsp": true in your VS Code settings).

#2818: Refactor error messages will no longer show an empty string "" for unnamed libraries, instead showing a relative path.
#2781: Signature help will now show “required” against parameters that are marked with the required keyword.
#2766: “Create missing overrides” will no longer sometimes generate invalid code on Windows.
#2762: The Dart: Sort Members command will no longer sometimes delete comments alongside imports.
#2680: The dart.analysisExcludedFolders setting is now supported for LSP.
#1132: The signature information popup will now appear automatically when typing ( and , in appropriate places (LSP).
#602/#2764: Loose .dart files can now be opened without a workspace folder (LSP).
#2727: The “Convert quotes” quick-fixes are now available for interpolated strings.

Commands

#2807: A new command Dart: Generate Documentation has been added to run dartdoc. This is also available when editing a dartdoc_options.yaml file and as a VS Code Task.
#2777: The error “Unable to execute Stagehand. SyntaxError” will no longer appear the first time you run Dart: New Project after upgrading your SDK.

DevTools

#2226: A new setting (dart.devToolsBrowser) allows launching DevTools in your default browser instead of Chrome.

Debugger

#2784: Hitting a breakpoint in a web app now jumps to the currect source code.

v3.14.1 2020-09-07

#2774: The Flutter SDK is now correctly located from a projects packages file when packages are read from .dart_tool/package_config.json.

v3.14.0 2020-09-03

Test Tree Improvements

#2623/#2731: The test tree now includes a summary of test states and total durations on Suite and Group nodes.

Flutter

#2697/#2725: A new command Flutter: Toggle Brightness allows toggling between Light/Dark themes (when using ThemeMode.system) while debugging your app.
#2638/#2743: If your Flutter SDK is missing its version file or Dart SDK (for example after a fresh clone or upgrade), activation of the extension will now be delayed while components are downloading (showing a progress notification) rather than reporting an error and requiring a restart.

Debugger

#2750: Running CLI apps using "console": "terminal" on Windows will no longer show “The terminal process terminated with exit code: 1”.
#2746: The message “Cannot read property ‘thread’ of undefined” no longer appears sometimes when ending a debug session.
#2699: When using “Debug my code” and an exception occurs with a call stack containing no user code, the top frame will now be selected to make it obvious that execution has paused.
#2690/#2730: Flutter scripts inside a folder named “web” are no longer incorrectly launched using the Dart-web debug adapter.
#2365: Automatic launch configurations (and those created with the “create a launch.json” option) will now scan your workspace for real projects instead of assuming your workspace is a single project at the top level.
#1876/#2711: Debug adapters now run out of process from the extension host. This should improve responsiveness when running many concurrent debug sessions as well as reduce the chances of some classes of bugs (shared state or leaking memory past the end of a debug session).
#1608: The Hot Reload command (and debug toolbar button) now only shows once an app has loaded the appropriate VM service extension.

Editor

#2744: The warning about modifying files outside of your workspace now also appears when using LSP mode.
#2734: The warning about modifying files outside of your workspace has been split into separate warnings for the Pub cache folder with its own setting (you can now set dart.warnWhenEditingFilesOutsideWorkspace and dart.warnWhenEditingFilesInPubCache individually).
#2696: CodeLens links should no longer cause the editor text to jump around during quick typing in the editor.

Commands

#2738: Output for commands like Flutter: Get Packages will now automatically be shown if the process is still running after a number of seconds.
#2698: A new command Dart: Reanalyze Project has been added that is intended to replace Dart: Restart Analysis Server (which will be removed in a future version). As with the restart command, frequent use of this command may indicate a bug in the analysis server and should be reported.
#2580: DevTools now runs embedded by default. This can be changed with the dart.embedDevTools setting.

Tasks

#2721/#2660: @szotp contributed fix for the error “The task provider for ‘pub’ tasks unexpectedly provided a task of type ‘flutter’” when using build_runner tasks in a Flutter project.

LSP and Analysis Server

These items only apply when running with the dart.previewLsp setting enabled and may require a very recent (or dev) SDK build. LSP will become the default in future, so please try it out and send feedback!

#2703: The Dart: Renalyze Project command is now available when running in LSP mode.
#2672: Code completion when using LSP is no longer empty when the cursor is in the whitespace before an identifier.
#1800: Editor lag/stuttering when using a VS Code extension that intercepts keypresses (for example Vim) should be significantly mitigated when running in LSP mode.

Documentation / website

#2115: Docs for add-to-app have been updated with a sample launch.json to allow attaching using a launch configuration (which unlike Flutter: Attach to Flutter on Device can include preLaunchTasks and other custom configuration).

v3.13.2 2020-08-05

#2702: Running Flutter apps using v1.20.0 of the SDK will no longer immediately fail printing “Exited (64)”

v3.13.1 2020-08-01

#2691: Hot Restart/Reload will no longer fail when using the debug toolbar button or command palette commands.

v3.13.0 2020-07-31

Improved Debug Discoverability

#2216/#2677: Launch configurations for common cases are now contributed dynamically based on the contents of your project. These show up when clicking the Show all automatic debug configurations link on the Run side bar when there’s no launch.json or by running the Debug: Select and Start Debugging command.

The configurations that show up are conditional based on your project (for example whether it’s a Flutter project, and whether it has tests). Clicking the cog icon will copy the launch configuration into your launch.json to allow you to customize if required.

#2676: Following new VS Code guidelines, a Run and Debug icon will appear in the editor toolbar when the active file can be directly run/debugged by the Dart extension.

Improved Handling of Unsupported Platforms

#2602/#2651: If the Flutter project you have open does not support a platform simply because its project files are missing (for example you have enabled web or desktop previews but are missing the web/macos folders), the relevant device will now show up at the bottom of the device selector as “Enable (device)”.

Selecting the device will allow you to easily run flutter create . in the project to create the missing files.

Embedded DevTools Improvements

#2655/#2661: When the Embedded DevTools preview is enabled, clicking Dart DevTools in the status bar will now allow you to select which DevTools page to open, or load DevTools in an external browser.

#2679: Additionally, DevTools will now use the same background color as VS Code as long as it’s dart/light enough to not cause contrast issues. This change requires a Dart DevTools release too so may not be visible immediately.

Test File Creation

#2650/#2662: The existing Go to Test/Implementation command has been extended and now also appears as a context menu entry labelled Go to Tests in the explorer tree.

If the related test file does not already exist, you will be prompted to create it.

The file created will contain a stub test that uses package:test or package:flutter_test depending on the type of the open workspace.

This functionality works best if your test files match the paths of your implementation files, swapping lib for test and adding a _test suffix to the filename.

Flutter

#2600: Quick-fixes like “Wrap with Column” now work correctly for multiline selections instead of only wrapping the widget from the first line.
#2606/#2615: Color previews in the gutter will now show only the first preview on a line instead of the last.
#2639: When using a new enough Flutter SDK, a small debounce delay when performing hot-reload has been removed (and instead moved to Flutter with a shorter delay).
#2586/#2599: A race condition that could cause a Flutter app run in Profile mode to hang on a white screen at startup has been resolved.

Editor

#2625: A new setting dart.enableSnippets allows disabling the built-in Dart and Flutter code snippets.
#2539: CodeLens links now appear above test methods even if package:test is added to the pubspec.yaml after the file was opened for the first time.
#2454: CodeLens links will no longer jump around as you type on the line above.
#2590: pub get no longer runs automatically for pubspecs modified inside dot-folders or the build folder.

Debugger

#2665: The limit on the number of toString() methods the debugger will call when inspecting values has been increased from 15 to 100.
#2635/#2637: A new setting dart.debugExtensionBackendProtocol allows switching from WebSockets to Dart SSE for the debug extension backend when debugging web apps using the Dart Debug extension and Flutter web-server device.
#2611: VS Code should no longer report “Timeout after 1000ms” when terminating a debug session.
#2683/#2684: szotp contributed a change to show full dart:developer log() messages without truncation.

Testing

#2619: Test durations shown in the test tree are now accurate and do not show the time taken since the start of the entire run.
#2609/#2614: Tests run from the test_driver folder will now automatically have the VM_SERVICE_URL enviroment variable set if an instrumented app is running.

LSP Preview

These items only apply when running with the dart.previewLsp setting enabled. This will become the default in future, so please do try it out and send feedback!

#2634: The analysis server log now includes the arguments used to launch the server in LSP mode.
#2633: When running in LSP mode, any output to the servers stderr stream is now correctly logged to the log file.

Other

#2627: The position of the Hot Reload button on the MacBook touch bar has been corrected.
#2636: A new command Dart: Open Extension Log provides an easy way to access the main extension log.
#2663: A new command Dart: Restart Analysis Server has been added. Please file bugs if you find yourself using this!

Docs

#2641: Using --dart-define in a launch configuration is now documented with an example.
#2514: Running Flutter in verbose mode is now documented.
#2497: Additional documentation was added for:

v3.12.2 2020-07-08

#2613: Flutter SDKs installed using Snap (snap install flutter --classic) will be automatically detected (and initialized, if required) on Linux.

v3.12.1 2020-06-30

#2592/#2597: The change to use standard DAP messages for debugger progress events caused events taking less than 500ms to not show (for example Hot Reload/Restart requests). This change has been partially reverted (pending a change in VS Code), though notifications will still only show in the status bar by default.
#2595: Log files will now correctly show activation status of the Flutter extension instead of always “(not activated)”.

v3.12.0 2020-06-25

Preview: Embedded DevTools

#1488/#2578: A new setting (dart.previewEmbeddedDevTools) has been added that allows running DevTools embedded inside the VS Code window. This feature is experimental and requires DevTools v0.2.6 or later.

DevTools will become disconnected when you stop a debug session but if you leave the window open, it will be automatically reconnected when you start a new debug session.

Cupertino Icons and Colors

#2150/#2149: Cupertino icons and colors are now rendered in the gutter in addition to Material icons and colors.

Debugger inspect()

#2137/#2560: Calling dart:developer’s inspect() function will now print the object to the Debug Console in an expandable form allowing properties to be examined similar to the variables/watch panels.

Note: This only works for non-Widget classes as the Widget Inspector also uses this function in order to navigate source code.

Improved Outlines

#2475/#2515: Both the Flutter Outline and standard Outline trees have been updated with some additional labels (including return values and text/icons for Text/Icon widgets).

Update Imports on Rename

#2482/#2507: The update-imports-on-rename functionality added in the last release is now enabled by default. Set "dart.updateImportsOnRename": false in your VS Code user settings to disable this.

Editor

#2579: Colors constructed using hex values (for example Color.fromARGB(0xff, 0xff, 0xff, 0xff)) will no longer show the wrong color in the gutter.
#2529: “Unknown Outline item! MIXIN” will no longer show in the debug console when editing documents containing mixins.
#2487/#2506: BootBlock enabled the “ignore lint quick-fix” by default (set "dart.showIgnoreQuickFixes": false to disable these).
#2163: The dart.previewNewCompletionPlaceholders setting has been folded into the dart.insertArgumentPlaceholders setting.
#1946: A one-time prompt will be shown offering to write the recommended Dart settings to your VS Code user settings file.

Commands

#2503: The PUB_HOSTED_URL environment variable is now used when checking for new versions of DevTools/webdev/Stagehand (this prevents update checks failing for some users - for example in China).

Flutter

#1850: Flutter’s structured error messages are now enabled at startup flag, avoiding a race condition that used to exist when enabling them after the app started.
#2582: Devices will no longer sometimes fail to be detected if another Flutter process had the Flutter startup lock when the device daemon was spawned.

Debugger

#2554: Restarting a dynamically started Dart debug session (for example from CodeLens or a test runner command) will no longer sometimes start a debug session using configuration from launch.json when clicking the Restart button.
#2541: BootBlock contributed a fix to stop sending multiple kill signals to the same process when ending debug sessions.
#2531: The prompt for a VM Service URL when attaching to processes now supports ws and wss protocols.
#2528: The “You have a breakpoint outside of your workspace” warning will no longer appear when you have set the debugger to break in SDKs/packages.
#2518: Debugger tooltips when hovering over a closure no longer show errors.
#2513: Running a Dart script in the terminal without debugging will no longer leave the debug session around even after the process ends requiring you to click Stop.
#2082: Running all tests using "program": "test/" in launch.json for Flutter apps will now automatically run without debugging (debugging while running all tests is not supported for Flutter).
#2496: When using the Web-Server device (and the Dart Debug extension) a better message will be displayed when waiting for the debug extension to connect.
#2516:/#2540: BootBlock switched the debuggers custom dart.progress events for standard debug-adapter-protocol progress events improving interopability for other editors using Dart-Code’s debug adapter.

LSP

Some issues have been fixed in the LSP server in the Dart SDK. These fixes only apply when using the preview LSP support ("dart.previewLsp": true in your VS Code user settings) and when using a new enough version of the Dart/Flutter SDKs (which may not yet include stable channels).

#2572: Go-to-Definition on an import that has an alias will no longer show multiple locations (one being the alias) and instead jump straight to the file.
#2535: Go-to-Definition on a var/final keyword will no longer show multiple locations (one being the variable name) and instead jump straight to the definition for the type of the varxiable.

Other

#2501: Many references to “Observatory” have been updated to “VM Service” to distinguish between Observatory (the Dart debugging web app) and the VM Service (an API for the VM).
#2565: A regression in VS Code v1.46.0 caused some “run without debugging” sessions to incorrectly run with debugging. This was fixed by the v1.46.1 release of VS Code.

v3.11.0 2020-05-29

Preview: Update Imports on Rename

#548/#1740: A new setting (dart.previewUpdateImportsOnRename) has been added to enable automatically updating import statements when files are moved/renamed.

This feature currently only works for files (not folders) and only a single file at a time (please add thumbs up to this VS Code issue!).

Improved Custom CodeLens for Tests and Main Functions

Improvements have been made to custom CodeLens for launch configurations. The existing template field on launch configurations has been deprecated and replaced with a new codeLens field.

#2459/#2466: A single launch configuration can now contribute multiple CodeLens links using codeLens.for.
#2458: A launch configuration can now specify that CodeLens links should only be shown within a sub-folder using codeLens.path.

For example, to add CodeLens for a launch config that sets a RELEASE_MODE=true environment variable to tests in test/integration_tests:

{
	"name": "Current File (release mode)",
	"type": "dart",
	"request": "launch",
	"codeLens": {
		// Types of CodeLens to inject
		"for": [ "run-test", "run-test-file", "debug-test", "debug-test-file" ],
		// Restrict to certain folders
		"path": "test/integration_tests",
		// Text for CodeLens link (${debugType} will be replaced with "run" or "debug")
		"title": "${debugType} (release)"
	},
	"env": { "RELEASE_MODE": true }
}

This will insert additional CodeLens links into tests, groups and main functions:

Global Expression Evaluation

#906/#1062: Expression evaluation in the Debug Console now works when not paused at a breakpoint/exception.

Evaluation is not currently scoped to the file/class you have open in the editor.

Commands

#2436/#2437: DevTools and other pub package updates are now correctly detected if they only vary by build metadata (+xyz), as described in Pub’s versioning scheme.
#2430/#2432: If DevTools fails to launch, the error notification now includes a button to try re-activating the package.
#2414/#2418: pub and flutter commands will no longer show .bat suffixes in the output window on Windows.

Debugger

#2428/#2469: When setting breakpoints in locations that will not be hit (for example in the Dart SDK when dart.debugSdkLibraries is set to false) a warning will be shown offering to change debug settings.
#2424/#2467: It’s now possible to attach to processes using a --write-service-info file. This allows running arbitrary commands to spawn Dart processes that Dart-Code does not support (as long as they can use --write-service-info) and attach to them in a single step using a launch configuration with a preLaunchTask.
#2471: When starting a debug session, the VM Service URL is now printed to the Debug Console.
#2448: Conditional breakpoints with expressions that evaluate to numerics now work for web apps.
#2423: When using a new enough Dart SDK (v2.9.0 onwards) it’s now possible to debug internal Dart libraries, such as dart:http.

Editor

#2468: Code completion now shows full documentation instead of only a summary.
#2426: Flutter Icons are now shown in the gutter when running in LSP mode.
#2425: Flutter UI Guides are now shown in the editor (if enabled) when running in LSP mode.

Flutter

#2453: For web apps, the Chrome device will now be picked over the Web-server device by default.

Testing

#2417: The test tree now shows test durations of the last run alongside the name.

Misc

#2422/#2427: More of the work to find project roots at startup is now async, reducing the chance of triggering “Extension causes high CPU” warnings in VS Code.
#2476/#2481: pub get will no longer automatically run when saving a pubspec.yaml file in a Bazel workspace.

v3.10.2 2020-05-16

#2464 Debugging apps using recent bleeding-edge builds of the Dart/Flutter SDK will no longer fail with Request must contain a "jsonrpc" key.

v3.10.1 2020-05-03

#2413 Ctrl(/Cmd)+Shift+F5 is no longer bound to Dart: Rerun Last Debug Session when already in a debug session, which prevented using the default Restart Debugging shortcut.

v3.10.0 2020-05-01

Main Function CodeLens

#2356/#2359/#2373 CodeLens links are now available on main() methods for both applications and test scripts. This allows running the current file even if the current launch configuration specifies another script. These links can be toggled using the dart.showMainCodeLens setting.

The template field in a launch config (see below for an example) has been extended to support templating these CodeLens.

run-test applies to test() and group() CodeLens, runs without debugging
debug-test applies to test() and group() CodeLens, runs with debugging
run-test-file applies to main() CodeLens in test files, runs without debugging
debug-test-file applies to main() CodeLens in test files, runs with debugging
run-file applies to main() CodeLens in non-test files, runs without debugging
debug-file applies to main() CodeLens in non-test files, runs with debugging

Run Tests on Device

#2363/#2374: A new launch config flag runTestsOnDevice has been added that allows you to create launch configurations that will run tests with flutter run on the select device instead of using flutter test.

Using the two features above together, you can add CodeLens links to easily run test scripts on a device:

{
	"version": "0.2.0",
	"configurations": [
		{
			"name": "Flutter App",
			"request": "launch",
			"type": "dart"
		},
		{
			"name": "Debug Tests on Device",
			"request": "launch",
			"type": "dart",
			"runTestsOnDevice": true,
			// This adds this config to CodeLens for test files
			"template": "debug-test-file"
		}
	]
}

Pub: List Outdated Packages

#2322/#2350: A new Dart: List Outdated Packages command has been added that runs pub outdated. It’s also available on the context menu and editor toolbar for the pubspec.yaml file.

This command will only show up when using >= v2.8 of the Dart SDK.

Custom Emulators

#1553/#2360/#2319: It’s now possible to add third party emulators that don’t show up in flutter emulators to the device selector using the dart.flutterCustomEmulators setting. The emulator must still show up in flutter devices once it’s been launched for it to be used to launch an app:

"dart.flutterCustomEmulators": [
	{
		"id": "my-emu",
		"name": "My Emulator",
		"executable": "/path/to/emulator",
		"args": ["--launch"]
	}
]

This setting also allows the command/args used to launch existing Flutter emulators to be overridden by using the same ID. For example, to force an existing Android emulator with the ID Pixel_2_XL_API_29 to run with -gpu host you can override its command/args:

{
	"id": "Pixel_2_XL_API_29",
	"name": "Pixel 2",
	"executable": "/Users/danny/Library/Android/sdk/emulator/emulator",
	"args": ["-avd", "Pixel_2_XL_API_29", "-gpu", "host"]
}

Editor

#1991: Holding <shift> when accepting code completions will now always insert completion text (rather than replacing text immediately to the right of the cursor). Which mode is default can be controlled by setting the editor.suggest.insertMode for [dart] in your user settings.
#2387: Errors and lints will now have clickable error codes (where available) to open a web page containing more information about the error/lint.
#2169: Key-binding is now available for both fixes and refactors (see refactorings and code fixes, though note that all IDs may not work unless you’re using a very recent SDK version).
#956: Closing Labels will now appear/disappear more reliably when enabling/disabling without restarting the editor.
#2323: Symbols are no longer doubled in the workspace symbol list if dart.additionalAnalyzerFileExtensions includes .dart or duplicates.
#2378: The Dart: Sort Members command now works when the LSP preview is enabled.

Debugger

#2146: Maps with complex keys (such as DateTimes) are now shown correctly in debug views like Watch and Variables.
#1990: The debugger Copy value action no longer adds " around string values.
#1246: Debug views will now automatically call toString() on complex types. This can be controlled with the dart.evaluateToStringInDebugViews setting.
#1021: The watch window will now show “not available” instead of an error message for variables that are not available at the current location.
#2389: Clicking the debugger Stop button too soon after starting a Flutter debug session should no longer result in the app continuing to build and launch. However, there may be a short delay before the process terminates.
#2403: Evaluating invalid expressions in the Debug Console will now show more specific error messages than “Expression compilation error”.
#2404: Trailing semicolons will now be ignored when evaluating expressions to avoid unnecessary expression compilation errors.
#2361: A warning will now be shown when launching an app if the casing of the cwd/program fields do not match the casing on the underlying file system.

Testing

#2380: Clicking Stop when paused in a test will now show a more obvious “Waiting for test to complete” notification.
#2385: Clicking Stop when paused in a test will now automatically disable breakpoints and resume the test to allow it to complete and the session to end cleanly.
#2362: test()s and group()s with variables in the name are now runnable from CodeLens links with some caveats.
#2349: Running tests from the test tree and with the Dart: Run Test at Cursor command is now possible even if another debug session is running.
#2351: The flutter_test package is no longer incorrectly marked as user-code so will not be debuggable when in Debug my code mode.
#2343: Running tests in the Dart SDK repo now (again) uses the VM directly.
#2335: Running tests in a folder named test for a non-web project will no longer show a spurious error about not being supported.

Commands

#2336: The Flutter: Run Flutter Doctor command no longer writes to an output window that is hidden by default.
#2377: The Dart: Run all Tests command now works when your projects are in sub-folders of the open workspace.
#2285/#2369: BootBlock contributed a new Dart: Rerun Last Test Session command which works like Dart: Rerun Last Debug Session but only considering recent test debug sessions.

Remoting Support

#2376: Joining a Live Share session will no longer show a warning about editing loose Dart files.
#2092/#2353: Flutter web debugging works when in a VS Code remoting session via the Dart Debug extension. This requires >= v1.18.0-5.0 of the Flutter SDK.

Other

#2310: Invalid log paths (eg. copied from other machines) no longer result in activation failures with cryptic error messages.

v3.9.1 2020-04-06

#2333: Previews of Flutter icons in gutter/hover tooltips have been restored.

v3.9.0 2020-04-03

Flutter: New Project Offline Mode

#1957/#2311: @ejabu Contributed a new setting dart.flutterCreateOffline that will cause Flutter: New Project to run in offline-mode.

Dart CLI Terminal Improvements

#2256/#2230/#2315/#2305/#2313: Running CLI apps in the terminal has received some improvements over the original release. Apps now run as real processes in a standard VS Code Terminal (instead of using a Pseudoterminal). This should resolve issues with certain keys (like backspace) not working correctly.

Note: You must be using Dart SDK v2.7.1 or later for this functionality to work.

Debugger

#2282/#2283: The debugger should no longer get stuck in the running state if it pauses very quickly after being resumed.
#2314: The debug adapter now users the debug adapter protocol’s runInTerminalRequest for terminal mode instead of proprietary events, improving compatibility with other editors.

Commands

#2289: Dart: Run Test At Cursor is now a little more lax about the positions of the cursor, including the whole start/end line for a group/test.
#2280: When running commands like Pub: Get Packages, the Output tab when no longer be shown automatically unless errors occur.

Editor

#2296: Code snippets should no longer force the editor into “snippet mode” unnecessarily, preventing code completion from working.
#2228/#2272: Flutter Outline now updates more reliably for files outside of your workspace.
#2218: Color previews now appear in the gutter for colors using the Color.fromARGB/Color.RGBO constructors.
#2140/#2270: Format Document should no longer break some unicode characters in long documents.

Testing

#2312: The Dart: Run All Tests command can now be used if you’re already in a debug session.
#2160: A new setting dart.allowTestsOutsideTestFolder controls whether files ending _test.dart outside of the test folder will be considered tests.

Preview: LSP

#2238/#2297: As part of ongoing work to migrate to the language server protocol, a new setting dart.previewLsp will force the analyzer to using the LSP protocol. This mode is not yet complete and has some known issues.

v3.8.1 2020-02-06

#2248: Completing simple named arguments will no longer trigger “snippet mode” which prevents code completion from activating.

v3.8.0 2020-01-31

Flutter Interactive Code Samples CodeLens

#2151/#2232: New in-line CodeLens links have been added to open the interactive code samples from Flutter widget definitions.

Clicking the CodeLens link will open the interactive sample from the API docs in your browser.

This functionality replaces the previous Flutter: Open Widget Sample command.

Restart Frame

#2171: The functionality included as Step Back in the previous release has been moved to the call stack as Restart Frame. This allows jumping back to other frames than the immediate parent.

Editor

#2131: The dart.previewNewCompletionPlaceholders functionality added in the last release is now enabled by default.
#2179: The Open in Xcode action now opens Runner.xcworkspace instead of (and falling back to) Runner.xcodeproj.
#2178: The Open in Xcode command now works even if the Xcode binary is named something other than xcode.
#2196: The Workspace Symbols list no longer shows filenames twice.
#2190: The Analyzing… status message is now hidden when the analyzer terminates.

Debugger

#2184: Invalid program paths in launch.json will now show a more descriptive message when trying to run so it’s clearer where/how to fix the issue.
#2165: The ${name} placeholder used in log file names will now be substituted with the device name when Flutter projects without a launch.json.
#2164: When running a CLI script using the terminal mode, output buffering is disabled.

Other

#2225/#2233: A warning will be shown if Flutter is installed in a protected folder on Windows that could prevent Flutter from functioning correctly.
#2162: Settings that contain log filenames/paths now use machine-overridable scope to prevent them being applied when connected to a remote workspace that may be a different platform.
#2143: The log file shown when the analysis server terminates now contains all log entries rather than just the General log category.
#1495: The Dart: Open DevTools command is now visible when not in a debug session and will show explanatory text if invoked.
#2157: CI builds have been migrated from Travis/AppVeyor to GitHub Actions.

v3.7.1 2019-12-11

#2166: Launching DevTools on a machine without Chrome will no longer open DevTools with an incorrect VM Service URI (https:// instead of http://).

v3.7.0 2019-12-05

Debugger Improvements

Preview: Web Debugging

Note: Flutter’s web support is still in preview and only be available on some channels. See the Flutter site for more info.

#1773: Basic debugging support is available for Flutter web apps when launching on the Chrome device.

Breakpoints, stepping through code and the variables list should work. Features that depend on expression evaluation are not currently available (this includes the watch pane, evaluation in the debug console, hovering over variables, conditional breakpoints). There may be a delay of a few seconds when hitting breakpoints - this is a known issue.

Debug Mode Toggle

#1291/#2121: While debugging, a new status bar will allow quick cycling through the settings to control whether the debugger steps into only your own code, your own code and Pub packages, or all code including the SDKs. Changing the option here will automatically update the dart.debugExternalLibraries and dart.debugSdkLibraries settings as well as immediately apply them to all running debug sessions.

Run Dart CLI apps in Terminal

#99/#2102: It’s now possible to run Dart CLI apps in the Terminal pane instead of the Debug Console. This allows you to provide input to the processes stdin stream. You can enable this mode by adding "console": "terminal" to your launch configuration.

When you run your app, the Terminal pane should become focused and the output will appear there. You can type directly into the terminal.

Note: This mode has less functionality than using the debug console (for example stack frames in errors cannot be linked to source code) so it is only recommended if you require this stdin functionality. This feature uses a VS Code Pseudoterminal to connect the Terminal pane to the debugger and is not actually spawning the process in a shell as would be the case if you ran it from the terminal directly.

Preview: Step Back

#2052/#2117: A new setting dart.previewDebuggerStepBack enables a new Step Back button on the debug toolbar. This function works similar to Step Out but moves the execution pointer to before the invoked function instead of after. This allows re-executing code without restarting your application.

Note: Enabling this setting also adds another button (Reverse Continue) to the debug toolbar. This is not functional but VS Code does not currently provide a way to add the Step Back button without also showing Reverse Continue (microsoft/vscode#85215).

Editor Improvements

Preview: Placeholders for @required Arguments

#2123/#2132: A new setting dart.previewNewCompletionPlaceholders enables improved argument placeholder functionality for named arguments annotated with @required.

IconButton has two @required arguments, which are now populated with placeholders that can be <tab>‘d between.

Additionally, enabling this setting will resolve some inconsistencies with tabstops for named/non-named arguments (#1940).

Note: The dart.previewNewCompletionPlaceholders setting is likely to become the default in a future update so please try it out and provide feedback. Insertion of placeholders can be disabled entirely using the existing dart.insertArgumentPlaceholders setting.

Other Editor Improvements

#2041: Flutter gutter icons and colors are now enabled by default.
#1709/#2116: Icons used in the gutter and Flutter documentation hovers are now shipped inside the extension so that they appear more quickly and work offline.

Flutter Improvements

#2134: Turning off dart.flutterTrackWidgetCreation will now explicitly send --no-track-widget-creation to Flutter in order to preserve behaviour when Flutter changes its own default for this flag.
#1589: Two new folder locations have been added to locations searched for the Flutter SDK, ./.flutter and ./vendor/flutter.
#2074/#2103: A new setting dart.previewHotReloadOnSaveWatcher will change hot-reload-on-save to watch for filesystem events instead of VS Code save events. This allows hot reload to be triggered automatically if external tools are making changes to Dart files.
#2120: dart.flutterHotRestartOnSave is now enabled by default. This means if a running Flutter app does not support hot reload, it will instead by hot restarted when the on-save handler fires.

Web Improvements

#68/#2113: When the program field of a launch configuration begins with web/, the webdev daemon debugger will be used when running the application. This makes it possible to run non-Flutter web projects (for example Angular web apps).

Testing Improvements

#2109: Adding testFailure to dart.openTestView now correctly selects the first test to fail in the tree rather than the containing suite node.

VS Code Remoting Improvements

#1866/#2047: When running in a container, the VM Service URI is now mapped through vscode.env.asExternalUri to allow DevTools to connect to it from the host/client.

Other Improvements

#1442: A lot of synchronous file system access has been updated to async. This should reduce blocking in the extension host and reduce the chance of triggering the “Extension causes high CPU” warning from VS Code.
#2087: The dependencies tree no longer writes errors to the console for projects that have a pubspec but no .packages file at load time.
#2096: Log files are no longer be overwritten with new empty logs during shutdown when there are pending actions that try to log after the logfile is closed.
#2138: In log filenames, the string ${name} will now be replaced with the debug session name to avoid concurrent debug sessions from writing over each others logs.
#2139: When using the Dart: Capture Logs command, any log lines that originate in a debug session will be prefixed with the debug sessions name to avoid confusion when there are multiple debug sessions.

v3.6.0 2019-11-01

Improved DevTools Integration

#1935/#1323/#1982/#1557: Integration with DevTools has had several improvements.

If an existing DevTools window is no longer connected to a debug session, launching again from VS Code will reuse that window in preference to spawning a new window. If an existing window is connected to the same debug session, launching again from VS Code will show a notification that will bring the existing DevTools window to the front when clicked.

Port numbers are now more predictable, starting at 9100 and increasing if that port is already taken (previously random port numbers would be chosen).

The debug toolbar has a dedicated button to launch the Flutter Widget Inspector. If you already have DevTools open and connected to the same debug session, it will navigate that window to the Inspector page rather than spawn a new window.

A new setting dart.openDevTools controls automatic launching of DevTools when you start a debug session.

The possible values are:

never: Never launch DevTools automatically
flutter: Launch DevTools automatically when a Flutter debug session begins
always: Launch DevTools automatically when a Dart or Flutter debug session begins

This setting can also be set at a workspace level (should you wish to apply it only to specific projects) and will reuse existing windows as described above.

Flutter

#2043: iOS Simulator names will once again be displayed in the status bar/device picker instead of the generic iOS Simulator label.

Preview: Flutter Gutter Icons and Colors

A new setting dart.previewFlutterGutterIcons has been added to enable the following gutter icons. If no issues are reported, these will be enabled by default in the next version.

#807/#2040: Flutter icon previews will appear in the gutter where they are referenced.

#2039/#2042: Flutter colour previews will now appear in the gutter of the editor for built-in Flutter colors and calls to the Color constructor.

Editor

#2011: Closing Labels will now update more quickly during typing. Previously a half-second delay was used to reduce the chance of them appearing in the wrong position during edits, but this is no longer required.

#2076: A new setting dart.enableMachineLearningCodeCompletion has been added to opt-in to the machine-learning backed code completion preview. Enabling this is equivalent to adding --enable-completion-model to the dart.analyzerAdditionalArgs setting.

#2067/#2046: Deprecated symbols will now be visually struck out in completion lists and in the code editor.

#1963: Deprecated symbols will be struck out in the Outline view.

Testing

#1871/#2060: A new command (which you can key-bind in the VS Code settings) has been added to jump between a file and its corresponding test file in the editor. This command will map lib/foo.dart to test/foo_test.dart and back. The command is only available when the current file can be mapped and the target file exists.

#2080: Opening a test file before restoring packages should no longer result in CodeLens action links not appearing for that file or tests failing to appear in the test tree after running.

#2055/#2053/#2054: Tests with quotes in their names can now be executed from the test tree, and also show test CodeLens action links.

Commands

#2024/#2037: Creating new projects with Flutter: New Project and Dart: New Project will now use the current-workspace SDK path (as selected with the Change SDK commands) for project creation, by writing the setting into the newly-created project’s VS Code workspace settings file.
#2083: Go to Symbol in Workspace should no longer sometimes go to the first line of the file instead of where the symbol is declared.

Debugger

#2034/#2021: Detection of test files has changed from being “anything that is in the /test/ folder or ends with _test.dart” to “anything that is both in the /test/ folder and ends with _test.dart”. This fixes some issues where running scripts from folders named test or scripts that are named _test.dart in the bin folder would be unexpectedly executed through pub.
#1992: The debuggers Variables window will no longer fail to render any class fields/getters if one of them returns an error.

v3.5.1 2019-10-02

#2029: When code-completing named properties, the cursor position will now appear in the correct (pre-v3.5.0) position.

v3.5.0 2019-10-01

Flutter

#2004/#2005: The Flutter: New Web Project command has been removed. To create web projects, you should now use the standard Flutter: New Project command. Note: Web support is still in preview, see the Flutter site for more info.
#1983/#1997: Running emulators will now show their friendly emulator name (as shown before launching) in place of their device names (for example “Pixel 2” instead of “Android SDK built for x86”).
#1994: Performing a Hot Restart while the debugger is in a pause state will no longer get stuck in a paused state when the app is actually running.

Performance

#1840/#2003/#1961: Scanning for projects is now asynchronous which should improve extension activation speed and reduce the chances of triggering VS Code’s “extension causes high CPU” warning.

Editor

#1958/#1959: Code completion will no longer include duplicates when the same item is imported via multiple libraries.
#1988: Saving a pubspec.yaml file that appears in the Explorer tree multiple times (due to overlapping multi-root workspaces) will now automatically run pub get instead of prompting as if it needs running for multiple projects.
#1973: pub get will no longer run automatically when pubspec.yaml files are modified inside a .dart_tool folder.
#1972: Prompts to run pub get are now disabled when working in the Dart SDK repository.
#1981/#2022: File extensions in the dart.additionalAnalyzerFileExtensions settings are now registered for additional editor functionality, such as Outline and Folding. This will allow analysis server plugins to provide additional functionality for non-Dart files.
#2007: The dart.analyzeAngularTemplates setting has been fixed to correctly registers editor functionality for HTML files when the Angular analyzer plugin is enabled.

Testing

#1971: Trying to run a whole group of tests will no longer fail with “Unable to start test for node with no test or group name”.

Other

#2002: Changing the SDK version back to Auto-Detect using the SDK picker will once again clear the workspace-level setting and fall back to searching PATH for an SDK.
#1717: SDK and log paths in settings are now categorised as machine-specific which will prevent them applying in remote workspaces where the remote may have different paths (or be a different platform).

v3.4.1 2019-09-04

#1967: Running tests from CodeLens links will longer report “Running the contributed command failed”.

v3.4.0 2019-09-03

Custom Test CodeLens

#1901/#1916 It’s now possible to create custom launch configurations for running your tests, for example to pass different arguments or environment variables to the test run.

These are standard launch configurations in a launch.json with the template field set to run-test or debug-test depending on whether you want to run in debug mode or not.

"configurations": [
	{
		"name": "Main application",
		"program": "bin/main.dart",
		"request": "launch",
		"type": "dart",
	},
	// Test launch config templates
	{
		"name": "Run in Browser",
		"request": "launch",
		"type": "dart",
		"template": "run-test",
		"args": [
			"-p",
			"chrome"
		]
	},
	{
		"name": "Debug in Browser",
		"request": "launch",
		"type": "dart",
		"template": "debug-test",
		"args": [
			"-p",
			"chrome"
		]
	}
]

Note: The launch config is used only when running from the CodeLens links and not when running from the test explorer context menu. This will be improved in an upcoming release.

Flutter Outline

#605/#961/#1932: The Flutter Outline tree added in the previous release is now enabled by default. Please continue to raise issues on GitHub with any issues or feedback.

This functionality can be disabled with the dart.flutterOutline setting.

Improved Flutter Errors

#1870/#1910: Support for improved Flutter error messages added in the previous release is now enabled by default. Please continue to raise issues on GitHub with any issues or feedback.

This functionality can be disabled with the dart.flutterStructuredErrors setting.

Flutter

#1924: The Flutter: New Project command will now create projects using Swift (iOS) and Kotlin (Android) by default. These can be configured with the dart.flutterCreateAndroidLanguage and dart.flutterCreateIOSLanguage settings.
#1943: A new setting dart.flutterAndroidX enables passing the --androidx flag when running the Flutter: New Project command.
#1905/#1909: A new setting dart.flutterAdditionalArgs allows custom arguments to be passed to all invocations of Flutter. For example, this allows passing --local-engine to enable running with a locally built engine.
#1933: The Flutter: Run Flutter Doctor command will now always run with the verbose -v flag.
#1919: A race condition that caused devices to stop showing up in VS Code for some users in the last version has been fixed.

Editor

#1931: Using VS Code key-bindings to open a filtered list of refactors was broken in the previous release by an optimisation but has now been fixed.
#1937: Opening a loose Dart file outside of any folder is not currently supported, but used to fail in silent and confusing ways. A suitable notification is now shown the first time this happens per-session.
#1944: A new setting dart.additionalAnalyzerFileExtensions allows additional file extensions to be included in analysis to help those developing analyzer plugins that handle non-Dart source files.
#1930: The extension keyword is now correctly colored.

Commands

#1302: A new command has been added Dart: Use Recommended Settings that will write some recommended Dart settings to your VS Code user settings (in the "[dart]" section). These settings address some common complaints around code completion and highlighting behaviour as well as enabling automatic formatting. Please try them out and send any feedback about these recommendations.
#1760: When Chrome is not installed, DevTools will now launch in the default browser instead and show a warning that it may be unsupported.
#1416: The Dart: Capture Logs notification is now shown as a progress notification which means it will no longer collapse into the bell icon after some seconds have passed.
#1906: A new command Dart: Stop Logging has been added that performs the same function as clicking Cancel on the logging notification.
#1917: Command output will no longer sometimes show [undefined] where the folder name should be.
#1897: The Open in Android Studio context menu item should now work more reliably across different versions.

Debugger

#1927: When editing a package that does not have its own entry points, pressing F5 without a launch.json will now check for an example/ project to launch instead of failing with an error.
#1911: Non-source stack frames in errors like <async suspension> are now dimmed like SDK frames instead of bright red.
#1942: Running scripts from the .dart_tool folder will now always run on the Dart VM (even for Flutter projects) to simplify debugging of code generator scripts.

Other

#1896: The Locate SDK button now correctly saves the folder you select to your user settings.
#1907: When running in a remote environment (for example using VS Code remoting functionality), browser windows spawned (for example when opening DevTools) will now automatically tunnel ports to avoid having to set them up manually.
#1384: In the latest VS Code release, a Dart icon was added to the default Seti icon theme 🎉.

v3.3.0 2019-08-02

Preview: Flutter Outline

#605/#961: Enabling the setting "dart.previewFlutterOutline": true will add a new Outline view to the side bar that includes the hierarchy of Flutter widgets in your build methods. Selecting a node in the tree will jump to the code that creates the widget and moving around the editor will select the appropriate node in the tree. Widget refactors are available on the context menu.

Note: The context menu will only appear if you first left-click the node to select it before right-clicking. This is a known limitation that we hope to address in future.

Improved Device Selector

#1809: The device selector has been improved and now contains both running devices and offline emulators in a single list. This list is always accessible from the device manager shown in the status bar and will also be shown if you try to launch an application without an appropriate device selected.

The list updates as devices are connected/disconnected and will be filtered to show only devices that are valid for projects in the current workspace.

#1867: When a device disconnects, a new device will only be auto-selected if it is valid for the current workspace.
#1863: Device selector will update automatically if devices/emulators are connected/disconnected/launched while it is visible.
#1781: Clicking the device in the status bar will always open the device selector (and include emulators) instead of only when more than one device is available.
#1768/#1810: Filter device selector when running projects to only devices that are available for that project.
#1864: Closing the device selector without selecting a device will no longer sometimes launch if a new device was connected while the selector was visible.

Preview: Improved Flutter Errors

#1870: Enabling the setting dart.previewFlutterStructuredErrors activates a new experimental feature for showing more concise error messages from Flutter. A summary of the error will be shown in red, followed by detailed information on how to resolve the issue (where available). Stack traces will show frames from your own code brighter than those from framework or SDK code.

Please try this feature out and send feedback via GitHub.

Other Flutter Changes

#1881: The “program” launch configuration attribute is now supported for “attach” configs.
#1568: Adding a Flutter project to an existing multi-root workspace (with File -> Add Folder to Workspace) will now automatically activate Flutter functionality. Removing the last Flutter project workspace folder will drop back to Dart-only mode.
#1848: Closing VS Code will no longer sometimes send multiple app.stop requests to Flutter which may result in processes not being cleaned up correctly.
#1892: If Flutter is unable to download the Dart SDK due to not having the required version of PowerShell on Windows, a suitable error will now be surfaced in the UI.
The Flutter: New Project From Docs command has been renamed to Flutter: Open Widget Sample to better reflect its intent to provide working code sample code and not a template for new projects.

Editor Changes

#1872: Errors in the Problems view may new include links to other locations (for example where a definition is duplicated). Note: This requires support from the Dart SDK that has not yet made it to the stable channel.
#1835: Enum values will no longer be duplicated in code completion multiple times when exported from multiple libraries but one library has already been imported.

Debugger Changes

#1849/#1869/#1824: Log events written with dart:developer’s log() function will now show in the debug console. This can be disabled with the dart.showDartDeveloperLogs setting.
#1845: Colors of text used in the debug console should now work better in a wider variety of light themes.
#1767: Evaluation requests in debug views (hover/watch/evaluate) are now sent concurrently and should complete much faster.

Test Runner Changes

#1823: Deleted/renamed tests are now updated after using the Dart: Run All Tests command.

Remoting Support

#1677/#435: Using Dart and Flutter in VS Code’s remote workspaces is now possible (for example Docker, WSL or SSH). Remote workspaces are still a preview VS Code feature so there may be issues, but please do open issues if you find things that don’t work correctly.

#1757: When running in a remote workspace, launching DevTools will fall back to launching the default local browser. Note: DevTools may not work in non-Chrome-based browsers and will still fail to launch if Chrome is not found when running locally.
#1738: Functionality that does not work when running remotely (for example launching emulators or opening Xcode) is disabled when running in a remote workspace.

Other Changes

#1830: The error message shown when DevTools fail to launch due to Chrome not being installed now mentions that it was trying to launch Chrome.
#1819: Startup performance has been improved that should further reduce “Extension causes high cpu load” warnings for slow filesystems and large folders.

v3.2.1 2019-07-16

#1859/#1843/#1843: Fixes a compatibility issue with the VM Service recently rolled into Flutter’s master channel that resulted in the Hot Reload command vanishing (and hot-reload-on-save not working).

v3.2.0 2019-06-28

Code Completion Improvements

#1776 & #1789: Code completion will no longer list a symbol multiple times if it can be imported through multiple libraries if one or more of them are already imported into the current file.

#1787: When auto-import completions require a prefix, the prefix will no longer abruptly appear in the completion label when it becomes the selected item.
#1786: Code completion will no longer sometimes list the same item multiples even for the same exporting library.
#1780: Code completion will no longer sometimes show undefined instead of the return type.
#1766: Sorting of code completion items when using auto-import-completions has been improved.

Flutter UI Guides Preview Improvements

#1791: Several improvements have been made to the Flutter UI Guides preview (see v3.1 release notes for instructions on how to enable) including fixes when using tab-indenting and better handling of joining lines.

Performance Improvements

#1741: The Dart and Flutter extensions are now packed with webpack which should lead to much faster startup performance, eliminating “Extension causes high cpu load” warnings at startup when filesystem access is slow.
#1750: Many improvements have been made to the performance of code completions when auto-import-completions are enabled.
#1800: Editor lag when using the VSCodeVim extension has been greatly decreased. It may not be possible to completely eliminate this lag due to the way VS Code and VSCodeVim interact (see this VS Code issue for details).
#1756: Cancellation tokens are now periodically checked during slow and async operations to short-cut work (for example in the case where the completion list is closed while the list was still being computed it will be aborted).
#1790: A minor memory leak when running tests has been resolved.

Editor Changes

#1779: Built-in types with lowercase names (like int, dynamic, boolean) will now be colored the same way as other types (like String and Future).
#1765: Syntax highlighting of code in doc comments with indentation has been fixed.
#1778: Hover tooltips will now render package URIs for the element in more places and more consistently.
#1745: Invoking Rename in invalid locations (such as on the name of a built-in library name in an import statement) will now show “You cannot rename this element” instead of a cryptic error message.

Flutter Changes

#1792: Flutter projects will now be detected nested more deeply in the workspace during activation.
#1795: Installing the Flutter extension with no Dart or Flutter SDKs in PATH will no longer immediately result in a prompt to install the Dart SDK.
#1755: Installing the Flutter extension with a Flutter project already open will no longer prompt to install the Flutter extension.
#1807: Web and Desktop devices will no longer be automatically selected at startup in preference to a connected mobile device/emulator.

Other Changes

#1785: Source maps for running Dart Code’s own tests have been fixed.
#1784: A typo in the emulator connection message has been corrected.

v3.1.0 2019-05-31

Preview: Flutter UI Guides

#1731: An early preview of Flutter UI Guides is available for testing/feedback.

You can turn this on using the dart.previewFlutterUiGuides setting. Some things to note:

The rendered lines may be broken/dashed depending on your editor line height. You can avoid the broken lines by adjusting your editor line height (for example "editor.lineHeight": 15). We’re looking for ways to avoid this (and would appreciate 👍s on this VS Code issue).
There may be a delay between modifying code and the guides updating. You may be able to reduce this delay by enabling dart.previewFlutterUiGuidesCustomTracking. Feedback on whether guides work better with or without custom tracking should be posted in this issue.
Enabling UI guides does not automatically turn off Closing Labels, so you may also wish to also disable dart.closingLabels.
You’ll need to restart VS Code (or run the Reload Window command) after changing the UI Guides settings for them to apply.

Please post all feedback about the UI guides feature here and add 👍 to this VS Code issue to show demand for improved VS Code APIs for features like this.

Flutter Changes

#1684: Flutter snippets are now available in Flutter web projects.
#1679: A new command Flutter: Clean Project has been added which calls flutter clean for the active project (using the active file as a hint when there are multiple, or falling back to prompting for a project).
#1673: Dart: Run All Tests no longer fails when there are multiple test suites in a Flutter project.
#1720: @ened contributed a new launch.json configuration property flutterPlatform to allow specifying the platform passed to Flutter with --target-platform.
#1638: The Debug: Attach to Flutter Process command has been split into Attach to Flutter Process (which prompts for a VM Service URL) and Attach to Flutter on Device (which will discover a Flutter process for a specific device). Most users will want to use the device version but the process version can be used to attach to other processes (for example Desktop, where Flutter views cannot be discovered).

Editor Changes

#1707: New material icons such as Icons.add_comment now render previews in tooltips.
#1707: Icon previews now use a color that renders well in both light and dark themes and as such the dart.theme setting is no longer used and has been removed.
#1694: Syntax highlighting has been improved (again) to handle additional comment character sequences.
#1678: Hovering over errors in the Problems view for files that are open but not visible will no longer result in flickering and high CPU.

Other Changes

#1719: The offer to fetch packages at startup will now look inside top-level folders for projects instead of only the roots of workspace folders.
#1732: Setting dart.sdkPath or dart.flutterSdkPath to a non-string values will no longer cause the extension to fail to activate.
#1725: The dart.env setting will now apply correctly at extension activation without having to trigger a config reload.
#1698: Setting dart.analyzerObservatoryPort will no longer sometimes cause the analyzer to pause and stop responding to requests.

v3.0.2 2019-05-13

Fix project type detection to not consider folders without pubspecs to be Dart projects.

v3.0.1 2019-05-09

A notification will be shown to take part in the Flutter Q2 Survey once it opens.

v3.0.0 2019-05-07

Flutter Web Projects

It’s now possible to create and run Flutter web projects in VS Code! 🎉

To get started, run the Flutter: New Web Project command from the command palette.

Once the project has been created and packages have been fetched, you can launch your web project like any other by pressing F5 or starting from the Debug menu.

If there are multiple potential debuggers for the current file, you may be prompted to select a debugger. If so, select Dart & Flutter. If the active file is a Dart file then this should be picked automatically for you.

Chrome will launch automatically and once the build completes the Flutter app will load.

Limitations

The current version of Flutter’s web support has some limitations, including:

No stateful Hot Reload (however Hot Restart is supported)
Breakpoints and stepping in the debugger is not yet supported via VS Code (you should use the browser dev tools for now)

If you’d like to automatically Hot Restart when saving, you can enable the dart.flutterHotRestartOnSave setting. This will cause Save to trigger a Hot Restart (only for projects where Hot Reload is not supported). Since Hot Restart is not stateful, this setting is not enabled by default.

Chrome OS Support

Developing Flutter apps on Chrome OS is now supported via Chrome OS’s Linux support - both for the Play Store and Flutter for web. To do this a little bit of setup is required:

To avoid having to run adb connect 100.115.92.2:5555 after each boot, you can enable the dart.flutterAdbConnectOnChromeOs setting to automatically run this when the Flutter daemon starts up.

Once this is set up correctly, Google Pixelbook should appear as an available device in the status bar and you can run your Flutter app with F5 or the debug menu. The application will run using Chrome OS’s support for running native Android apps.

The Dart DevTools and Widget Inspector are fully supported here too. Run the Dart: Open DevTools command to launch them.

Flutter Web Projects

Flutter for web is also supported on Chrome OS but requires Chrome be installed in the Linux container (see the setup notes). Once this is installed you can follow the Flutter for web notes above to create and run Flutter web projects.

Limitations

On Chrome OS, only a specified set of ports from the Linux container are available at localhost from the main Chrome OS browser. This means that in order to use DevTools in the main Chrome OS browser fixed ports must be used for both the DevTools server and the VM service. This is enabled by default but comes at the expense of not being able to run multiple apps at the same time (since they’ll try to bind to the same port). If you need to run multiple apps you can disable the dart.useKnownChromeOSPorts setting (but if you want to use DevTools you’ll then need to install Chrome in the Linux Container - see the setup notes above).

Additionally, for Flutter web projects, the limitations mentioned above in the Flutter for web notes also apply.

Other Changes

#1505: DevTools should now reliably open in Chrome regardless of default browser.

v2.26.1 2019-05-01

#1651: When multiple pubspecs change at once (for example during a git branch change), a prompt will be shown offering to fetch packages (sequentially).
#1659: pub get will no longer fire multiple times concurrently during creation of projects with Dart: New Project and Flutter: New Project.
#1666: Projects created with Flutter: New Project will once again show the device selector in the status bar without having to reload the folder after initial creation.

v2.26.0 2019-04-26

Auto-Importing from Code Completion

#1060: Code completion now lists symbols that are not yet imported and will auto-import the required library when selected.

Items will show “Auto import from xyz” in their details when this will occur.

The import will be added once the selected item is committed. This also works for part files, where the import will be added to the relevant parent file.

This feature requires v2.2.1 of the Dart SDK and can be disabled with the dart.autoImportCompletions setting.

Improved Dependencies Tree

The dependencies tree has been updated and improved. It’s now (#1591) be available for workspaces that have multiple projects (either in sub-folders, or as part of a multi-root workspace), (#1622) sorts folders above files and (#1621) no longer shows projects in their own dependencies list.

Flutter Changes

#1634: A race condition that caused devices not to be detected has been resolved.
#1593: The prompt to install the Flutter extension when opening a Flutter project has been streamlined and can install the extension for you instead of just linking to the marketplace.
#1629: A new command Flutter: Toggle Check Elevations has been added to toggle highlighting invalid elevations.
#1602: Running without debugging no longer stops some Flutter functionality (such as debug toggles) from functioning.
#1574: Progress notifications will now appear more quickly when launching Flutter applications.

Debugger Changes

#1566: Adding breakpoints in SDK files while debugging will no longer throw errors.
#1540: The Hot Reload button on the debug toolbar (and Touch Bar) is now placed next to the Restart button.

Editor Changes

#1625: Flutter snippets now appear in completion for Flutter projects that are in sub-folders of the main workspace.
#1598: Creating projects with Stagehand will no longer sometimes end with the VS Code explorer pane showing a stale file list.
#1594: Switching between SDKs will no break some functionality inside files that were already open.
#1573/#1635: More improvements have been made to syntax highlighting of comments.
#1570: The “Ignore hint xxx” quick-fixes (enabled with dart.showIgnoreQuickFixes) will now appear at the bottom of the Code Actions list.
#1563: Documentation tooltips will be positioned more appropriately for Widget constructor calls that span many lines.
#1555: Diagnostic errors in the Problems list have more detailed descriptions of how to resolve them.
#1444: @macro declarations in tooltips will now be resolved to the correct values (when using a recent enough version of the SDK).

Other Changes

#1637: pub get will now run for pubspec.yaml changes made even outside of VS Code. For example, if you switch Git branch and the pubspec is modified, packages will be fetched automatically.
#1538: DevTools now defaults to the dark theme. This can be changed with the dart.devToolsTheme setting.
#1450: pub get will automatically run immediately after creating stagehand projects.
#1633: Update notifications are no longer shown after the first install.
#1604: The Hot Reload buttons/commands will no longer show up when running a Flutter project without Hot Reload support.
#1640: A new setting has been added (dart.flutterHotRestartOnSave) that will enable running Hot Restart on save when running a Flutter project without Hot Reload support.
#1600: Enabling the (diagnostic) Analyzer observatory port will no longer result in an error showing in the console.
#1599: Optional settings are now defined as such so that editing them in the VS Code Settings UI does not update them to default values for the data type (such as 0 or "").
#1618: Notifications for Dart DevTools will no longer be shown when running tests.

v2.25.1 2019-04-17

The required version of Dart DevTools was increased to v0.0.15

v2.25.0 2019-03-29

#1493: A new Hot Reload button (thunderbolt icon) has been added to the debug toolbar. As part of this change, the Restart button will now always Hot Restart and the existing setting to control this behaviour has been removed. In the current version of VS Code it’s not possible to change the position of this custom button, however it will be moved next to the Restart button in an upcoming release.

As a result of the Restart button now always being Hot Restart the keybindings have changed. The new keybindings are:

Ctrl+Shift+F5 (macOS: Cmd+Shift+F5) - Restart Debugging / Hot Restart
Ctrl+F5 - Hot Reload

macOS Touch Bar Support

#936: New buttons have been added to the macOS Touch Bar during debug sessions. Buttons are available for the Flutter: Hot Reload, Dart: Open DevTools and Flutter: Take Screenshot commands.

As with the debug toolbar, the Hot Restart button will move next to the Restart button in an upcoming release.

Better Theme Support

#1050: A new option - dart.theme - has been added to inform the Dart extension whether you’re using a Light or Dark theme (unfortunately VS Code does not expose an API for this). This controls the color of the icons shown in tooltips (and maybe more in future).

#1496: Similarly, the dart.devToolsTheme setting will let you control which theme is used for the Dart DevTools. For now the default is light, however this may change to default to whatever dart.theme is set to in future when the Dark theme is more polished.

Flutter Changes

#1537: The samples show in the Flutter: New Project From Docs command are now delegated to Flutter to ensure they better align with the Flutter channel you’re using.
#1473: Some issues with the Flutter: Save Screenshot command failing based on the open file have been fixed.

DevTools Integration Changes

#1525: Installing pre-release versions of DevTools using pug global activate will no longer result in additional prompts to install DevTools when trying to launch.
#1514: The error message shown if you try to launch DevTools when running without debugging is now less vague.
#1511: DevTools processes will be cleaned up more reliably when closing your project/VS Code.
#1504: A keybinding of Ctrl+Alt+D has been added to launch DevTools
#1500: DevTools updates are now detected without requiring an update to the VS Code extension.
#1478: DevTools is now updated automatically once you have approved the initial install.

Debugger Changes

#1533: Breakpoints will no longer trigger during expression evaluation.
#1512: Framework stack frames in error messages in the Debug Console will now be faded.
#1502: Stopping at breakpoints will now always show the top frame, even if it’s inside code marked as not-debuggable.
#1497: The debugger will no longer treat local (eg. path) packages as external, meaning they will now be debuggable by default.
#1475: Triple quotes in logpoints are now handled correctly.
#1449: Running a test that outputs an Observatory banner in non-debug mode will no longer cause the debugger to connect to that URL and behave unexpectedly.
#178: For new versions of the SDK, comments will appear in SDK files while stepping into them.

Editor Changes

#1543: A new setting dart.enableSdkFormatter has been added to allow disabling the built-in SDK formatter.
#1521: The “Open in Android Studio” command now works correctly on Linux.
#1498: Nested /* multi-line */ comments are now colored correctly.
#1554: Lines that contain a /// triple-slash comment that come immediately after another line with a triple-slash comment will no longer be entirely colored as a comment if there is code preceding the triple-slashes.
#1483: Code completion will no longer remove preceding spaces.
#1494: Typing : and = will no longer immediately trigger code completion (since they are usually followed by whitespace).

Commands Changes

#1545: The Dart: Capture Logs command will no longer sometimes drop Observatory events for a short period after starting a debug session.
#1403: A new command Dart: Open Analyzer Diagnostics has been added to start/open the Analyzer diagnostics web app. This is a diagnostic tool that you may be asked to use when trying to diagnose issues you’ve reported.

Other Changes

#1491: The first time document formatting fails due to syntax errors, a notification will be shown explaining the reason.
#1472: A new setting dart.env has been added that allows setting/overriding environment variables for all spawned Dart/Flutter processes.
@tsangint contributed #1466: The extension will no longer fail to activate if the working directly contains broken symlinks.

v2.24.0 2019-02-27

Dart DevTools Integration (inc Flutter Inspector)

A new command Dart: Open DevTools has been added that allows you to launch the Dart DevTools for a debugging session. With a debugging session active, open the command palette and find the DevTools command.

The first time you run this (and subsequently when the DevTools package is updated) you may be prompted to activate or upgrade.

Clicking Activate/Upgrade will run pub global activate to activate the DevTools package for you.

If you have multiple debugging sessions active, you’ll be prompted for which one to open DevTools for.

DevTools will launch in your browser and be automatically connected to your debug session. For more information on the functionality of Dart’s DevTools see the DevTools docs.

While the Dart DevTools are active, you’ll see them in the status bar of VS Code. Clicking will re-launch your browser as long as there’s a suitable debugging session.

v2.23.1 2019-02-21

A bug that resulted in SDK detection failures if you had a folder named flutter inside your project has been fixed.

v2.23.0 2019-02-15

Dart: New Project

A new command Dart: New Project has been added that works similar to the existing Flutter: New Project and Flutter: New Project From Docs commands:

This command uses Stagehand to provide project templates. If you’ve not activated Stagehand before you’ll be prompted to do so the first time you use it. Clicking Activate Stagehand will automatically run pub global activate stagehand for you.

You’ll be presented with a list of project templates from Stagehand. The templates you see may vary based on the version of Stagehand you have activated.

After selecting a template you’ll be prompted for a name and folder and your project will be created and opened automatically.

Customizable Debugger Restart Button Behaviour

The restart button on the debug toolbar is now customizable for Flutter debug sessions.

In the VS Code user settings you’ll find an option named Flutter Debugger Restart Behaviour which allows you to change the behaviour of the restart button (and corresponding command/menu items) between Hot Reload and Hot Restart. The default behaviour remains as hot reload (though depending on feedback this could change in future).

Improved Project Picker

When running a command that requires a project root (for example Pub: Get Packages) that isn’t clear from your active file, you’re prompted for a folder. The built-in workspace-folder picker has been replaced with one that shows only Dart projects and can include sub-folders.

Improved Flutter Build Progress

The build progress shown during a Flutter build has been improved and now remains on-screen for the whole duration of the build rather than appearing and disappearing at each build step.

Flutter Extension Reminder

If you don’t yet have the Flutter extension installed, you’ll be reminded to install it when you open a Flutter project. In the future, some Flutter functionality will migrate from Dart to the Flutter Extension so installing it now will avoid any disruption.

Other Changes

Hot-reload-on-save no longer fires in Profile/Release builds resulting in “unsupported” messages being displayed.
deviceId is now considered a valid in launch.json for attach configurations.
Newlines have been restored to Flutter error messages that were lost in the previous version.
The Flutter: Upgrade command now works correctly when you do not have a Dart/Flutter project open
Running pub get when saving pubspec.yaml will now be delayed by 10 seconds if the file was auto-saved.
Using the Firebase Flutter plugin should no longer show “Invalid JSON” messages in the debug console.
Code completion now performs better when typing : after a named argument.
Single-line Dartdoc directives (like {@macro some.cryptic.value}) will no longer appear in tooltips.
Performance of moving your cursor around when on a slow (eg. remote) file system is improved and should reduce the chance of “Extension host not responding” messages.
Debugger toggles are now synced when another debugger is attached to the VM.
“Unknown instance kind: Null” will no longer appear in the debug console when hovering over a null variable during debugging.
A previous bugfix for ignoring dart binaries in PATH that were not real Dart VMs has returned (without the additional bugs).
Symlinks to dart in PATH that are not in a folder named bin will no result in a failure to find the SDK.
A new setting dart.buildRunnerAdditionalArgs has been added to allow passing additional args to build_runner tasks:
```
"dart.buildRunnerAdditionalArgs": [
    "--delete-conflicting-outputs"
]
```

v2.22.3 2019-01-31

A bug that caused Flutter’s Hot Reload to stop working if there were breakpoints in invalid locations has been fixed.

v2.22.2 2019-01-29

A bug that prevented unhandled exceptions in Dart CLI apps being shown in the debug console has been fixed.

v2.22.1 2019-01-25

The change to ignore dart binaries in your PATH that are not from the Dart SDK has been reverted because it broke handling of SDKs that came from symlinks in PATH. It will return in a future update minus the breakage.

v2.22.0 2019-01-25

Flutter: New Project From Docs

It’s now possible to create sample projects from the Flutter docs directly in VS Code with a new command Flutter: New Project From Docs.

This command will list the sample projects currently available in the docs.

Selecting a sample will automatically run flutter create --sample {sample ID} and open the project for you.

Note: This functionality requires both v2.22 of the Dart extension and v2.22 of the Flutter extension. While it’s currently possible to develop for Flutter with only the Dart extension, this may cease to be the case in future as more functionality migrates to the Flutter extension so if you haven’t already, you should install it.

Clickable Stack Trace Locations 🎉

Dart and Flutter stack traces in the Debug Console now have clickable links!

Run Test at Cursor

New commands have been added to run/debug the test for the current cursor location. The command is available in the same locations that the test CodeLens is available (the command will not be visible if your cursor is not in a valid location). For info on how to add key bindings, see here.

New Refactors

A new Extract Local Variable refactor has been added.

This extracts the code under the cursor into a variable and will allow you to type over its name.

There’s also a new Convert Method to Getter refactor to convert argument-less methods to getters.

Prompt to Launch with Errors

The preview setting from the previous release is now named dart.promptToRunIfErrors (no preview prefix) and is enabled by default. This will result in a prompt when launching if errors exist in your project.

Type Hierarchy Previews

The Show Type Hierarchy command has been updated and will now preview the relevant code as you move the selection up and down the list.

Editor Changes

The Rename input box will now appear over the symbol to be renamed when invoked on a keyword (such as the prefix for imports, and the class/constructor names for new, const keywords)
Code completion should no longer pop open showing Flutter snippets when typing in comments
Code completion should now update correctly when typing spaces after arguments
A new setting dart.analysisExcludedFolders (a string array) has been added to allow excluding folders from analysis
Git dependencies that point to sub-folders of repositories will now show more accurate paths in the document symbol list
Code completions that insert multiple lines (such as @overrides) will now insert with the correct indentation
Code blocks in dartdoc comments will no longer show in different colors depending on the indentation level
Syntax highlighting has been improved
- Functions with type arguments should now be colored the same as those without
- covariant is now recognised a keyword
- Nested multiline comments will now color correctly
Only currently-visible documents are now considered priority by the analysis server (rather than anything that had been opened recently)
The “editing files outside your workspace” warning has had some tweaks
- It now refers to open workspaces as “Open Folders”
- It will no longer show if you do not have any folders open
- It has a “Don’t Warn Me” button that’ll hide it forever
- The long path has been removed

Command Changes

Running Flutter: Fetch Packages will no longer prompt you for a project a second time if you cancel the first prompt
The Flutter: Fetch Packages command will no longer sometimes contain “unwanted”)}” characters in the prompt message

Debugger Changes

The Locals pane will no longer spin forever when stopped inside functions with type arguments
Flutter runtime errors are now categories as stderr and will be colored accordingly in the Debug Console
Stack frames will no longer show [Unoptimized] prefixes in the call stack
Flutter will now automatically run with the --verbose flag when logs are being captured with the Dart: Capture Logs command

Other Changes

Having a dart binary in your PATH that is not the Dart VM will no longer result in activation errors
HTTP_PROXY and NO_PROXY will now be included in log headers to help troubleshoot proxy issues
The display of file/paths in the test runner has been tweaked
The Create Emulator option will now always show in the device selection list, ignoring text filtering
Timestamps are now supplied to the analysis server to allow monitoring of latency via the Diagnostics app
Several MB of dependencies have been removed which should result in faster extension activation times

v2.21.1 2018-12-05

A regression introduced in v2.21.0 that resulted in a Path must be a string error when launching a debug session with no open files (and no output pane) visible has been fixed.

v2.21.0 2018-11-28

Preview: Prompt to Launch with Errors

A new setting dart.previewPromptToRunIfErrors has been added that will prompt you before launching if errors exist in your project.

This will become the default behaviour in future so please try it out and open issues if it fires when you would not expect.

Improved Completion Icons for Folders/Files

Code completion for imports now shows file and folder icons from your VS Code theme.

Run All Tests in Launch Config

It’s now possible to create a launch config in launch.json that runs all tests (the same functionality as the Dart: Run All Tests command) by setting the program property to the path of a test folder. Unlike the command, this can be run with or without debugging (F5 / Ctrl+F5) whereas the command always runs without the debugger.

{
	"name": "All Tests",
	"type": "dart",
	"request": "launch",
	"program": "tests/", // or tests/foo for a subset of tests
}

Other Changes

The Flutter: Save Screenshot command now works when multiple devices are connected, taking the screenshot from the device selected in the status bar.
Launch configs cwds are now considered when detecting project entry points.
A warning will be shown if a launch config contains a variable that cannot be resolved.
The deviceId field now shows in completion for launch configs and will not generate a warning when used.
The labels in the SDK picker have been moved around so that long paths are less likely to be truncated.
Opening a .code-workspace file that contains paths that do not exist will no longer cause the extension to fail to activate.
The warning Unknown kind: MIXIN when writing code using mixins will no longer be printed to the dev console.
An incompatibility with the Bracket Pair Colorizer 2 extension that resulted in font ligatures not working correctly for => has been resolved.

v2.20.0 2018-11-02

The Flutter: Inspect Widget feature that was added in v2.17.0 but disabled in v2.17.1 due to bugs is now re-enabled by default when using Flutter version v0.10.2 or later. This command allows you to tap on a widget on your device/emulator to highlight it and jump directly to the source code where it was constructed.

Lint Names in Problems View

VS Code now natively shows lint names and error codes in the Problems view so the dart.showLintNames setting has been removed.

Quick-Fix for Ignoring Lints/Hints

A new setting dart.showIgnoreQuickFixes (default: false) has been added that will add quick-fixes for ignoring lints and hints to the lightbulb menu.

These fixes will also show up in the Problems View.

Don’t Format Specific Files/Folders

Since VS Code does not allow per-folder/file settings, it’s now possible to stop certain files/folders from being formatted with the dart.doNotFormat setting. The setting is an array of string globs that are checked against the full file path.

"dart.doNotFormat": [
	"**/*.g.dart",
	"**/generated/**",
	"**/Google/flutter/**",
]

Note: Until this VS Code issue is implemented, this will stop both format-on-save and explicit Format Document calls from formatting.

Collapsed Call Stacks

When running in VS Code v1.29 (due in the next few weeks) stack traces will collapse “non-debuggable” code (based on your dart.debugSdkLibraries and dart.debugExternalLibraries settings).

Preview: build_runner Tasks

If you enable the dart.previewBuildRunnerTasks setting and your project references build_runner in its pubspec.yaml then new tasks will be registered with VS Code. You can find these by running the Tasks: Run Task, Tasks: Run Build Task, Tasks: Run Test Task commands in the palette. The tasks will appear as pub or flutter depending on the type of projects you have open.

Running the watch task will keep build_runner running in the background, re-building files as required when you save changes. If you wish to have the task run automatically when you start debugging you can add it as a preLaunchTask in your debug configuration.

Preview: toString() Calls in Debug Views

It’s now possible to force the debugger to call toString() on classes when displaying them in debug views (this includes the Variables pane, the Watch pane, tooltips and inline debug views) with the dart.previewToStringInDebugViews setting. This feature is experimental and may have a performance impact.

Before

After

Other Improvements

Flutter projects in immediate subfolders of the workspace folder are now detected and will force the editor into Flutter mode.
Formatting of text in progress notifications shown when Flutter is downloading SDKs/packages has been improved.
Tooltips will no longer show dartdoc directives like {@tool xxx}.
Completing function names on an import/export line will no longer try to insert argument placeholders as if you were calling the function.
Code completion will no longer pop open when typing colons in case statements.
Code completion will no longer pop open when typing spaces outside of argument lists.
Code completion for method/function calls with no argument placeholders will no longer get stuck in “snippet mode” causing further completions not to work until you press <escape>.
CodeLens links for running tests will no longer appear inside test files for projects that do not support being run with pub run test (for example the Dart SDK repository).
The “Create File” refactor no longer displays an error when invoked.
Setting the debugger to break on All Exceptions will no longer pause inside threads running framework snapshots (such as during package:test startup code).
Debug sessions should no longer remain active until the Stop button is clicked when Dart script fails to compile.
Terminating commands like pub get repeatedly should no longer result in orphaned progress notification messages.
PubCache and AppData folders are now excluded from analysis should you open your entire user directory in VS Code.
The prompt offering to run pub get when the .packages file is missing/out-of-date will no longer appear for Fuchsia projects.
The dart.runPubGetOnPubspecChanges setting now defaults to false for Fuchsia projects.
The path topaz/tools/prebuilt-dart-sdk/${platform} has been added to the top of Dart SDK search paths for Fuchsia projects.

Note: This version requires VS Code v1.28 (up from v1.27).

v2.19.0 2018-10-01

Flutter Attach

Functionality has been added to attach to existing applications (for example a native Android app hosting a Flutter view). To attach, ensure your device is connected but the Flutter view to attach to has not yet been created. Then run the Debug: Attach to Flutter Process command from the command palette.

This will begin monitoring the device waiting for a Flutter view to start.

Now load the app and/or interact with the app to cause the Flutter view to be created. This will enter a normal debug session that supports all of the usual Flutter functionality (inc. Hot Reload, Hot Restart, debug toggles).

To detach from the debug session, click the Detach button on the right side of the debug toolbar.

For more information on adding Flutter to your existing app, see this page on the Flutter Wiki.

Current Limitations

It’s not currently possible to attach to a Flutter view that has already been created.
Breakpoints in startup code may be missed because the code may execute before breakpoints are initialised (you can temporarily work around this by putting a delay in your startup code).

Debugger Improvements

Scripts inside bin/ or tool/ folders will now always run directly on the VM and not through flutter run even if inside a Flutter project.
An issue where debug sessions might continue to run in the background after clicking the Stop button on the debug toolbar has been resolved.
A new command Dart: Rerun Last Debug Session has been added to the command palette. This command is bound to Ctrl+Shift+F5 (macOS: Cmd+Shift+F5) and will rerun the previous debug configuration. This is particularly useful if you use the Run/Debug CodeLens test links or run your “current file” and wish to rerun the same file/test(s) after navigating to a different file.
A rare race condition that could result in a failure to attach the debugger has been fixed.

Code Editing Improvements

Icon previews in tooltips/completion have been fixed for the Flutter master channel which had started rendering HTML chunks.
Syntax coloring now understands the mixin keyword.

Other Improvements

Long-running commands like pub get now have a cancel button on the notification.
A Scheme is missing error that sometimes appeared in the console if .packages contained relative paths has been fixed.
The dependency tree will now reappear if you remove the second-to-last workspave folder from your workspace (it shows only when there is exactly one workspace folder).
Using the Dart SDK from Flutter for simple Dart projects/libraries will now display “Dart from Flutter {flutter SDK version numer}” in the status bar instead of an incorrect/stale Dart SDK version number.
A warning about multiple breakpoint responses should appear in the console less often (but is not entirely eliminated yet).
The Dart: Capture Logs command will now use a VS Code-provided log folder rather than prompting. When you stop capturing logs the file will open and you can use Save As to save it to another location if desired.

Note: This version requires VS Code v1.27 (up from v1.26).

v2.18.0 2018-08-31

Debugger Improvements

It’s now possible to set environment variables via a launch.json property (env) for debug sessions
Support for VS Code’s new terminateRequest call has been added to allow graceful debugger shutdowns and reduce the chance of orphaned processes
The working directory will now be set more reliable when using a relative path in a launch.json’s program property
Arrays are once again sorted numerically in Variables and Watch windows
Asserts are now enabled by default for VM projects and can be controlled with the enableAsserts property in launch.json
The Flutter: Inspect Widget command will now jump to the correct location (user code, not framework code) on Windows

Test Runner Improvements

Files are now only considered tests if they are in the root test/ folder or end with _test.dart
Running a single test file and then the Dart: Run all tests command will no longer result in duplicate test nodes in the tree
Suite icons in the tree should no longer disappear if you stop a test run mid-execution
Test results from previous test runs will now be faded out to make it clearer which results are from the most recent run
Test files that fail to produce any results will no longer leave a “loading…” node in the tree

Editor Improvements

Quick-fixes that create files (eg. Create file on an import that doesn’t exist) are now supported
Dart snippets now work with VS Code’s editor.tabCompletion feature which allows pressing <tab> to complete snippets even when the completion list is not open
The code completion list will no longer consider the (…) characters when filtering as you type

Other Improvements

Dart SDK update checks will no run for Dart SDKs being used from a Flutter SDK even if being used in a non-Flutter project
Log files capture with the Dart: Capture Logs command will now include the VS Code version number at the top
The Dart SDK update notification now has a “Disable update checks” button that will disable updating checking (this sets the dart.checkForSdkUpdates setting)
Running pub/flutter commands from within the editor will print the correct folder name in the output instead of sometimes strings like ../..

v2.17.1 2018-08-04

Signature Help will only trigger automatically when pressing ( or , if the dart.triggerSignatureHelpAutomatically setting is enabled (this may become default again in future when some issues are resolved)
dart.trackWidgetCreation - which powers Flutter: Inspect Widget has been disabled by default while some issues are investigated
Silent extension restarts should no longer fail when the Testing CodeLens is enabled

v2.17.0 2018-08-02

When debugging a Flutter application a new command Flutter: Inspect Widget appears in the command palette which allows you to tap on a widget on your device/emulator to highlight it and jump directly to the source code where it was constructed.

Note: In v2.17.1 dart.trackWidgetCreation - which powers this feature - was disabled by default while a bug is investigated. You can enable this but may find issues when hot reloading. flutter clean after enabling the setting may resolve these issues. This setting will be re-enabled by default once these issues are fixed.

Testing Improvements

CodeLens links now appear above tests and test groups that allow you to quickly run/debug an individual test or group without running the whole suite.

Several other improvements have been made to the test runner:

When running a test suite that has previous results, the previous results will become faded until they are replace with new results to give an indication of progress through the suite
Test results for a suite should no longer vanish from the tree when you run a subset of that suites tests
Tests should not appear duplicated in the tree if run as part of a while suite and then subsequently individually
To reduce scrolling, test names are no longer prefixed with their group names in the tree
Test suites with failures will now move to the top of the tree
The Output pane will now update real-time if selected for a test that is currently running

Flutter Screenshots

@timsneath and @Ramalus contributed a Flutter: Save Screenshot command to save screenshots from your device/emulator. The first time you use it in a session you’ll be prompted for a folder to save to (you can suppress this with the dart.flutterScreenshotPath setting) and shown a notification to quickly open the folder. This command can be bound to a key in your VS Code key bindings the same as any other command.

Signature Help

Signature help is now available to quickly look up arguments to functions without having to hover over them.

Signature help can be invoked with Ctrl+Shift+Space (macOS: Cmd+Shift+Space) or if the dart.triggerSignatureHelpAutomatically setting is enabled, will appear automatically when you type ( or ,.

This feature relies on a new feature in the Dart SDK. At the time of release this is available in the Flutter master channel but not yet on dev/beta channels.

Other Changes

A new setting dart.enableCompletionCommitCharacters has been added to allow committing code completion with (, [, ,, .) keys (this will become the default in a future release)
dart.sdkPath no longer takes priority over Flutter’s local SDK for Flutter projects
A warning will be shown if you attempt to modify a file outside of your workspace (for example because you Go-to-Definition’d to a framework file)
Long variables that were previously truncated when using Copy Value from the Watch pane’s context menu should no longer truncate; however this also requires a VS Code fix (fixed in Insiders at time of release, but expected in Stable very soon)
A new setting dart.maxLogLineLength has been added to control the truncation of long lines for all log files (setting to null will disable truncation - logging lots of long lines may affect performance!)
All log files will now include SDK version numbers at the top (if they are available at the time of opening the log file)

v2.16.0 2018-07-16

Create Emulators

Emulators can now be created directly from the device selector.

The emulator created will be based on a standard Pixel device and named automatically.

This feature is only available when using a very recent Flutter SDK. Flutter’s master channel already has the required functionality but it may take a little longer to filter through to the beta channel.

Flutter Update Notification

When a new version of Flutter is available you’ll now see a prompt in the editor.

Clicking the Upgrade Flutter button will execute flutter upgrade inside the editor and once complete automatically reload the SDK in the background.

This feature requires a recent version of Flutter that provides better update checking; therefore you might not see this prompt on the next update if you’re on the current beta channel. Updates are only checked every few days so you might not see the prompt immediately when a new version is available.

Dart Test Runner

The test runner included for Flutter in the previous version is now enabled for Dart projects. This will only work for tests that can be run with pub run test and therefore will only activate if there is a .packages and a pubspec.yaml file in the project root.

Faded Dead Code

Unused imports/variables and dead code are now flagged to VS Code and will render slightly faded. You can control this with the editorUnnecessaryCode settings as described here.

Other Changes

Projects in sub-folders (for example in an example folder) will now launch more reliably when pressing F5 without needing to create a launch.json
Whether the test view will be shown automatically on test runs can now be configured with dart.openTestView (an array that can be empty, or a combination of testRunStart and testFailure)
Data provided to the VS Code Outline tree should now contain more accurate code ranges for each symbol and show parameter information for the selected node
Commands like Sort Members and Organize Imports no longer rely on an active text editor, resolving issues when using Folder Source Actions or VS Live Share extensions
Paths searched for SDKs at startup are now logged to the extension log to aid troubleshooting
Error messages shown at startup (such as when failing to locate an SDK) will now include a Show Log button to review extension logs
Go-to-Implementation now works from call sites in addition to declerations
When terminating a test debug session and the test framework is allowing time for the current test to finish, a message will now be shown in the Debug Console (clicking the Stop button a second time will force immediate termination)
Debugger tooltips/watch info for Type instances will now show the type name instead of just the word Type
Launching a Dart VM script with cwd set to a Flutter project in the launch config will now correctly use the Dart debugger, not the Flutter one
The Workspace Symbol list should now jump to the selected symbol more reliably
Pressing F5 with an open file that it outside of the project containing the selected debug configuration should no longer result in a failure to launch
Comments within import/export statements will no longer break syntax highlighting for the rest of the file
A new setting (dart.analyzerSshHost) has been added that allows running the analysis server over SSH on a remote machine to reduce latency when working on a remote file system (such as using SSHFS)

v2.15.0 2018-06-29

Test Runner

A new test runner has been added that will render test results in a tree in the Test Side Bar.

Currently there is no detection of tests so they will only appear once you start running them which can be done with F5/launch.json, using the Start Debugging/Start Without Debugging options on explorer context menus or using the new Run All Tests command (noted below) to run all test files.

Clicking on a test will open the Output pane if there is any output from the test and also navigate you to the test in the source (note: navigating to the source required a change in Flutter which is currently only available on the master channel).

Note: By default this is only enabled for Flutter projects. You can opt-in for Dart projects by setting the dart.previewTestRunnerForDart setting to true though there may be some edge cases where this currently does not work correctly.

Run All Tests

A new command has been added to quickly run all tests in your project (the equivalent of flutter test or pub run test). This command will spawn a concurrent debug session for each workspace folder that contains tests.

Go To Implementation

Go To Implementation has been implemented to allow you to quickly jump to implementations from abstract members/interfaces.

Quickly Open in Android Studio or Xcode

New context menu entries have been added to ios and android folders to allow you to quickly open them in Xcode or Android Studio.

Filtered Extension Logging

The Dart: Capture Logs command has been extended to allow selection of which log categories to include when troubleshooting or reporting issues in the extension.

Other Changes

Handling of concurrent Dart or Flutter debug sessions has been improved and commands that work on a specific debug session (for example Open Observatory) will now prompt you to select a session
throwing plain instances like Strings will now show correct values in the Variables > Exceptions debugger pane instead of only the fields of the instance
Evaluating expressions in the Watch pane will now time out after 1 second to avoid hanging when no response is received
Launching debug sessions from multi-root workspaces where there are no launch.json files has been made more reliable
Copy Value in the Variables and Watch debugger panes should no longer truncate the values added to the clipboard
Additional instances of exception messages being truncated in the debugger have been resolved
Log files created using the Dart: Capture Logs command will now be prefixed with some information about the SDKs that have been loaded
Workspace symbols are now assigned more accurate ranges
Refactors that edit multiple files are less likely to record multiple undo steps

v2.14.0 2018-06-14

Outline View

VS Code 1.24 includes an Outline preview feature. This version improves the data provided to Code to allow rendering the symbol data in a tree.

Getters in Debug Views

Debugger views such as Variables, Watch and tooltips will now include getters as well as fields.

This is enabled by default but since getters could have side-effects you can disable this per-projects using the dart.evaluateGettersInDebugViews workspace setting.

Complete Statement

A new Dart: Complete Statement command has been added. This command will attempt to finish the current line you’re editing by adding things like closing brackets and semicolons before moving the cursor to the next line. You can bind this command to a key by running the Open Keyboard Shortcuts command in the command palette.

Daemon Progress Notifications

After installing a Flutter update via flutter upgrade or switching channel with flutter channel the first invocation of Flutter will download dependencies and build tools. If this hadn’t happened before opening VS Code then this would happen quietly in the background when Dart Code invoked the device daemon which resulted in unexpected behaviour (for example no devices being detected or delays in launching). Now when this happens, Dart Code will show notifications of what’s happening in the background so it’s clear why devices haven’t been detected (yet).

Improved Termination of Processes

A number of issues with terminating Dart and Flutter processes have been resolved, including:

Clicking the Stop Debugging button during a Flutter app build should cancel more quickly and no longer sometimes still result in the app running
flutter run and flutter test processes should not persist after clicking the Stop button
flutter daemon process should not persist after closing VS Code

Some of these fixes rely on support from the Flutter tools which means they only work when using a very recent Flutter SDK. Flutter’s master channel already has these changes but it may take a little longer to filter through to the dev and beta channels.

Simplified Diagnostic Log Capturing

A new command has been added to simplify collecting logs when reproducing/reporting issues in Dart Code/Flutter/Dart. It’s named Dart: Capture Logs in the command palette.

You’ll be prompted to select a location/filename for the log file and then a notification will appear informing you that logs are being captured.

When you click Stop Logging the resulting log file will be opened in the editor for you to review before you attach to a GitHub issue. Currently this file will include all types of logging (Analysis Server, Observatory, Flutter Run, Flutter Test, Flutter Daemon) so you should start it as close to reproducing your issue as possible. The option to select which log sources to capture may be added in a future update.

Other Changes

The Please connect a device or select an emulator prompt should no longer show if you connected your device too quickly after pressing F5
Saving a file while a Flutter app is launching will no longer result in a Hot Reload failure message
Saving non-Dart files while debugging a Flutter app will no longer trigger a Hot Reload
Modifying settings that cause a silent extension reload (such as log files) will no longer stop Hot Reload from working
Exception text shown in the Debug Console will now be truncated at 6 lines instead of 100 characters
Exception messages can now be copied from the Variables and Watch debug views
Non-debuggable stack frames will now be rendered greyed in the call stack
The workspace symbol list is now truncated to 500 items to avoid some performance issues in VS Code rendering thousands of items
Empty files will no longer result in errors from the document symbol provider
The selected document/cursor position after a refactor that edits multiple files should now be more appropriate
Some additional (minor) memory leaks have been fixed
Windows drive letter normalization is now enabled by default (and can be disabled with dart.normalizeWindowsDriveLetters)
Settings for log files now support relatives paths
Folders for log files will now be created automatically if they don’t exist

v2.13.2 2018-06-06

A memory leak in code completion has been fixed, so Dart Code should no longer get slower over time

v2.13.1 2018-06-05

If you have only a single emulator it will no longer immediately launch upon pressing F5, instead showing the usual prompt to give you the option of connecting a physical device
Using the Create method 'xxx' quick fix to create methods in classes in other files will no longer incorrectly insert the code into the current file
Completions for methods that already include arguments such as setState will no longer have additional parenthesis added on to the end
The new keywords have been removed from Flutter snippets
Relative paths for Flutter test scripts in launch.json will now correctly be detected as tests and not try to run on devices

v2.13.0 2018-06-01

Emulator Launching

Emulators can now be launched directly from within Code. If you start debugging without a connected device you’ll be presented with a list of emulators on your system to launch.

After selecting a device a notification will appear while the device boots and connects.

You can also trigger the emulator selection by clicking on No devices in the status bar or by running the Flutter: Launch Emulator command from the command palette.

This feature relies on support from the Flutter tools which means it will only show emulators when using a very recent Flutter SDK. Flutter’s master channel already has this change, but it may take a little longer to filter through to the dev and beta channels.

Improved Folding

Code folding is now handled by Dart Code rather than being done by VS Code based on indenting. This should result in more accurate folding regions and also allows collapsing file headers and directives.

This feature relies on support from the Dart analysis server which means it will only activate when using a very recent SDK. Flutter’s master channel already has this change, but it may take a little longer to filter through to the dev and beta channels.

Flutter: New Project Improvements

New settings have been added to customize the Flutter: New Project command:

dart.flutterCreateOrganization: Used in Java package names and as prefix in the iOS bundle identifier
dart.flutterCreateIOSLanguage: The programming language to use for IOS apps (objc or swift)
dart.flutterCreateAndroidLanguage: The programming language to use for Android apps (java or kotlin)

Debugger: Conditional Breakpoints and Log Points

You can now set Conditional breakpoints that will only break if the provided condition is true.

Log Points are like Breakpoints but rather than pausing execution they simply print() the message and then continue. This allows you to add debug information without having to insert print()s and reload the application or revert them when committing code. Like breakpoints, they also persist across sessions.

Debugger: Start from Explorer

You can now run specific scripts directly from the Explorer pane using the Start Debugging and Start Without Debugging options on the context menu. This bypasses what’s in launch.json and uses default behaviour for the given file (this includes selecting the correct debugger based on whether the script looks like Dart or Flutter and is in a test folder).

Debugger: Attach to Process

@stuartmorgan contributed Dart: Attach to Process which allows attaching the debugger to an existing process that you have an Observatory URL or port number for. You can configure this in your launch.json by setting request to attach or by simply running the Debug: Attach to Dart Process command.

You can also provide the observatoryUri in launch.json to skip this prompt when launching with F5.

Note: In this version the standard Dart debugger is attached, which means Flutter-specific functionality like hot reload will not be available.

Other Debugger Changes

Setting vmAdditionalArgs in launch.json allows you to pass custom arguments to the VM when launching Dart applications
Lists and Maps will now render consistently between the Variables Watch debugger panes
Adding List and Map entries to the watch window is now more reliable and Add to Watch will be disabled for items where it is not supported
@tfriem contributed including indexes in the display of Map entries in the debugger Variables and Watch panes to avoid items with identical display text being de-duped by VS Code
@tfriem contributed displaying complex Map keys in the debugger Variables and Watch panes
Debugger tooltips will now show more descriptive type names (eg. String in addition to _OneByteString)
Stepping into SDK sources while debugging will no longer cause analysis server exceptions
Full Restart has been renamed Hot Restart
A race condition that could cause unwanted Continues during debugger startup has been fixed
A race condition that could cause debugExternalLibraries/debugSdkLibraries settings to not apply correctly has been fixed
Resolving variables like ${workspaceFolder} inside program and cwd in launch.json has been improved and now better supports launching programs from sub folders
launch.json now supports relative paths and does not require ${workspaceFolder} prefixes for program or cwd
On Windows, Dart VM processes for CLI apps should be cleaned up better when clicking the Stop button on the debug toolbar
The Observatory Log File will now include launch information for the process, including arguments

Editor Changes

Organize Directives has been renamed to Organize Imports as this is now a shared action across languages in VS Code
A Refactor option is now available on the context menu for improved visibility (the items shown are a filtered list of the existing lightbulb menu)
The Organize Imports action now appears in the Source Action context menu
The Sort Members action now appears in the Source Action context menu
The dart.organizeDirectivesOnSave setting has been removed in favor of Code’s new codeActionsOnSave functionality. To achieve the same functionality you can set the following in your settings:
```
  "editor.codeActionsOnSave": {
      "source.organizeImports": true
  }
```
Rename is now supported in more places (for example if you press F2 on the class keyword it will rename the class or on an import it will add or edit the prefix)
Tooltips for types from external packages will now show the package name at the top of the documentation
The completion list will now refresh when typing a / or \ inside an import path to provide completion for nested folders/files
Keywords will no longer highlight incorrectly if followed by an opening paren (eg. if(1))
Opening Git diff views will no longer incorrectly use the original file for analysis

Other Changes

A prompt to open release notes will now show when Dart Code is updated
A warning will be shown if the casing of the folder you have opened differs from that on the underlying disk as this may cause unexpected analysis errors from consolidating package: and relative paths
Changes to most log file settings will no longer require an extension reload
Using --preview-dart-2 for the Dart VM will no longer give errors about not being compatible with checked mode
Running Flutter: Get Packages in the Flutter repository will now run flutter update-packages
Prompts to upgrade folders in your workspace will no longer appear after a “silent” extension restart
The Dart SDK version number has been removed from the status bar from Flutter projects (it was incorrect but may return in future)
A workaround has been implemented to resolve an issue where Flutter commands like Hot Reload would not work if the Visual Studio Live Sharing extension was installed due to the way it proxies debug sessions
The dart.previewDart2 setting (and associated launch configuration property) is no longer supported by Flutter and has been removed (if you were using this for CLI apps you can add --preview-dart-2 to vmAdditionalArgs and/or analyzerAdditionalArgs)
Running scripts from nested folders will now more accurately detect the type of project/script being run and as a result the prompt to upgrade folders to “Workspace Folders” has been removed (you can still manually add folders as Workspace Folders if desired)

v2.12.0 2018-04-26

Support for Flutter Profile and Release Modes

You can now create launch configurations for profile and release modes for Flutter apps. For now, this requires you to create a launch.json and set the flutterMode argument.

For more information on using profile and release modes, see Running Flutter Apps in Profile or Release Modes.

Flutter Memory Usage Monitoring

When running a profile build (or if you set showMemoryUsage in your launch configuration) the total memory for your applications heaps will be shown in the status bar.

Note: This is heap usage and not total process memory. In debug builds it may not be reflective of actual usage in a release build.

Progress Notifications for Long Running Tasks

Long running tasks like Flutter: Get Packages and Flutter builds will now show more obvious progress notifications with progress animations.

As part of this, these actions may also now be cancelled from the x in the notification.

Flutter Icons in Tooltips and Completion Descriptions

Flutter icons now show correctly in tooltips and completion descriptions instead of chunks of HTML.

An Extract Widget refactor is now available on the lightbulb menu that creates a new Widget class and inserts a call to its constructor in the original position.

Extract Method Refactor

An Extract Method refactor is now available on the lightbulb menu.

Better Feedback for Failed Renames

Failed renames will now show errors directly in the editor instead of window-scoped notifications that require dismissing. In an upcoming VS Code release we will stop the rename input box from appearing at a location that does not support a rename.

Preview: Better Handling of Windows Paths

A new setting (dart.previewExperimentalWindowsDriveLetterHandling) has been added. Setting this value to true will cause all drive letters to be converted to uppercase when Dart Code interacts with services like the analysis server. This should fix a number of issues affecting Windows users (unexpected errors like Type 'x' cannot be assigned to type 'x' or completion and errors not updating when referencing code with package: imports). In future this behaviour may become the default so please try it out and send feedback.

Other Changes

Exception messages shown in popups during debugging are no longer truncated
Pressing F5 in a Flutter project will no longer pick bin/main.dart to execute over lib/main.dart
More output from flutter run will be shown in Debug Console
The display of lists and maps in the debugger variables pane has been improved
The Add to Watch action on variables (in the debugger variables pane) will now correctly populate watch expressions
Slow Mode Banner is now known as Debug Mode Banner
@343max contributed a dart.flutterSelectDeviceWhenConnected setting to control whether to automatically select the most recently connected device in Flutter projects (defaults to true to preserve current behaviour)
Organize Imports is now bound to Alt+Shift+O by default
A new dart.organizeDirectivesOnSave setting has been added
CPU usage while moving the caret/selection around the editor should be much lower
Code’s automatic indentation detection will be disabled for Dart since sometimes it picks 4 spaces based on line continuation indenting
A new Go to Super Method command has been added
Find References will now also include the declaration
TODOs will once again appear in the Problems pane if you set the dart.showTodos setting to true
Formatting of the hover tooltips has been improved
Tooltips will no longer show on import prefixes (there was no useful information in them)
Duplicate code fixes will no longer show in the lightbulb menu when there are multiple on the same line
@aemino contributed a fix for ligatures not working correctly on => due to them being considered individual tokens
Analysis of AngularDart now enabled by default (requires a v2 dev SDK) and can be controlled with the dart.analyzeAngularTemplates setting
The error message shown when the analysis server fails to start will now be more appropriate

v2.11.2 2018-04-05

--no-preview-dart-2 will no longer be sent to the VM (even when dart.previewDart2 is set to false) for CLI apps as it is not supported

v2.11.1 2018-03-27

SDKs in paths that contain spaces will no longer report that the analysis server has terminated

v2.11.0 2018-03-27

Flutter Test

Basic support for flutter test has been added. If you launch a file (by pressing F5 with no launch config, or by setting program in your launch config) that is inside the test folder of a Flutter project, the script will be run using flutter test. Output will appear in the Debug Console pane. All debugging functionality (breakpoints, etc.) should work as normal.

Flutter Test

Projects in Sub-Folders

When projects are found in sub-folders you will now be prompted to mark them as Workspace folders. This will allow Dart Code to better understand which folders are projects when detecting which debugger to run when pressing F5.

Projects in Sub-Folders

Note: VS Code will duplicate these workspace folders in the top level of explorer - please +1 this VS Code issue to allow this to be configurable.

Silent Extension Reloads

Many operations in Dart Code require re-initialising the extension. This was previously done by prompting the user to "Reload Window" which resulted in a visible disruption and all extensions re-initialising. In this version Dart Code silently re-initialises itself meaning no more prompts for actions such as changing SDKs. Since this operation still terminates and restarts the Dart analysis server it may take a few moments to re-analyze your project.

SDK Picker for Flutter

The Flutter version number now appears on the status bar and allows quickly switching SDKs by clicking onit (this functionality already existed for Dart). Set the dart.flutterSdkPaths setting to an array of SDK folders (or folders containing SDKs) to use this. Note: This does not change your Flutter channel but relies on having multiple versions of the SDK in different folders (you can do this without multiple clones by using git worktree as shown in our Travis script).

SDK Picker for Flutter

Other Changes

dart.previewDart2 now explicitly sends --no-preview-dart-2 when set to false to allow opting-out of the Dart 2 preview once it becomes the default (if undefined, neither flag will be sent)
The setting dart.previewDart2 now works for Dart CLI apps in addition to Flutter (note: your Dart SDK must support it, which currently means you must be using a v2.0 dev release)
Pressing F5 without a launch.json will now launch more scripts without configuration (scripts inside test, bin and tool)
Errors when launching Flutter projects (such as when you have not accepted Android licenses) will now appear in the Debug Console
Flutter’s Hot Restart is now bound to Ctrl+F5 by default during a debugging session
Flutter: New Project will now validate that you do not call your project flutter or flutter_test which would lead to confusing errors about depending on itself
The flutter/flutter repository will once again be treated as a Flutter project rather than a Dart one, meaning it will use Flutter’s version of the Dart SDK and start the flutter daemon
The extension will no longer crash if you try to opened a Flutter project without a Flutter SDK but with a Dart SDK in your PATH
The display of the workspace symbols has been updated to include file paths in addition to class names
The document symbol list will no longer list constructor invocations within Flutter projects
The document symbol list (Ctrl+Shift+O) now uses the same API as the workspace symbol list (as updated in the previous version) when your SDK supports it, resulting in more consistent rendering between document/workspace lists
Running Pub: Get Packages, Pub: Upgrade Packages, Flutter: Get Packages or Flutter: Upgrade Packages directly from the command palette will now switch between flutter and pub based on the project type
Commands like Pub: Get Packages will no longer fail if your Dart SDK is in a folder with parentheses in the name
Code completion will no longer insert unwanted parentheses or colons that already exist ahead of the cursor when typing quickly
Code completion for named arguments will no longer insert placeholders but instead automatically re-trigger code completion where the value should be provided
Dart and Flutter version numbers will no longer show in the status bar when the active file is not a Dart file
The SDK quick-picker will now include your current SDK even if it’s not included via the dart.sdkPaths/dart.flutterSdkPaths settings
The SDK quick-picker will now longer show an error if configured folders contain symlinks to Dart binaries
A new option (dart.vmAdditionalArgs) has been added to pass custom arguments to the VM when launching Dart CLI apps
Code completion will no longer get stuck open after typing @override

v2.10.0

When the Dart or Flutter SDK could not be located, a “Locate SDK” button is shown to allow browsing to the SDK manually
The Flutter: Run Flutter Doctor command is now available outside of having a Flutter project open
Many Flutter debug toggles (debug painting, performance overlay, debug mode banner, slow animations) will now persist across a Hot Restart
Exception tooltips will now show the toString() of the exception rather than just the type name
Exception information will now show in the Variables debugger pane
Searching for symbols across the workspace now uses a much faster API (this requires a very recent SDK build and will fall back to the slower method for older SDKs)
The dependency tree explorer now shows file icons
Refactorings from the lightbulb menu are now keybindable! See the readme for full details
The Flutter SDK is now correctly detected from the .packages file of a project on Windows
If your Flutter SDK does not yet have a cached Dart SDK a more appropriate message will now be shown
Code completion tabstops may now provide more specific completion suggestions for some actions
A spinner will now be shown in the status bar during Flutter build progress messages
Previously hidden settings for debug log files are now visible to aid completion/validation when setting them

v2.9.2

Running Flutter: New Project will no longer complain about missing SDKs if dart is not in your PATH

v2.9.1

A more appropriate error message is now shown when running Flutter: New Project when Flutter cannot be found

v2.9.0

A new command (Flutter: New Project) has been created to simplify the process of creating and opening a new Flutter project (unlike others, this command is in the palette even without a project open)
Flutter and Dart debuggers have been merged, you will no longer be asked to choose between Flutter and Dart when running new projects!
- As part of this, the type attribute on launch configurations in your launch.json will be automatically changed from dart-cli/flutter to dart upon opening the project
Flutter projects no longer require a launch.json file if being launched with default arguments; if you hit F5 in a project without one it will just launch immediately
If your packages are missing or out of date you will be prompted to run pub get/flutter packages get upon loading your project (this can be disabled with the new dart.promptToGetPackages setting, which can be set at the folder level)
Snippets have been added for Flutter widgets (stless, stful, stanim) and will show only inside Flutter projects
Quick Fixes and other code actions that insert code now support tab stops and selections (for example the Wrap with new widget assist will now select the text widget for you to type over)
Code completions will no longer insert parentheses/argument placeholders if they are already present
Code completions will now longer insert named argument placeholders if a value is already present
A spinner will be shown in the status bar during analysis
A spinner will be shown in the status bar while Flutter/Pub commands are running
Quick fixes will now be sorted in the lighbulb menu by the severity of the error that they fix
Quick fixes and code assists are now categorised as QuickFix and Refactor in Code to allow for keybinding a specific type
SDKs will now be listed by version number in the SDK picker
Snippets will no longer be prioritised over other completions in the completions list
A workaround for a change in VS Code 1.20 that causes breakpoints to not be hit on Windows has been implemented
Package restore commands will now be terminated and re-run if you invoke them again while they are already running (this includes if you change pubspec.yaml and save)
Due to a number of issues with the implementation, external files (SDK, packages) will no longer open read-only (this behaviour may be restored in some form in future)
Executing package restore commands in a workspace that has no pubspec.yaml on Windows will no longer get the extension stuck in a loop
Saving pubspec.yaml in a Dart project will no longer run flutter packages get if you have a Flutter project in the same workspace
Running Flutter: Get Packages will no longer sometimes unexpectedly ask you for the workspace folder to run the command in
Opening a Dart file outside of a folder will no longer show errors in the developer console
A new setting (dart.previewDart2) has been added which allows you to opt-in to Dart 2 behaviour such as optional new/const (you must be using an SDK that supports this!)

v2.8.2

Code completion has been updated to use a new field provided by the analysis server that allows the text to be inserted to be different from the text displayed in the completion

v2.8.1

Code 1.20.0 included a change that broke debugging for projects without a launch.json. A fix is on its way but in the meantime a workaround has been added to restore the ability to debug. As a consequence you will need to select the correct debug type twice when first debugging a project with no launch.json but this will be addressed in a future update (after Code’s fixes are live).

v2.8.0

Code completion will automatically trigger when manually typing import " to help complete package/filenames
Code completion will automatically trigger in the correct location when completing the import ""; snippet to help complete package/filenames
The document symbol list will no longer fail to load for documents returning CONSTRUCTOR_INVOCATION symbols in results
Code completion will no longer fail to load for documents returning CONSTRUCTOR_INVOCATION symbols in results
The debug adapter should no longer crash if you print() JSON that looks like a flutter command while debugging a flutter application (additional improvements over those already made in previous releases)
Debug status text like “Initializing hot reload” will no longer remain visible if you terminate a debugging session while it is visible
The “Hot restart recommended” hint has been moved from an information bar at the top of the window to the status bar
Pressing the debuggers Restart button to perform a hot reload will no longer crash if you have unsaved changes
Invoking Save All will no longer cause multiple hot reload requests which could result in crashes
If a hot reload is requested while another is in progress, the message “Reload already in progress” will be displayed in the debug output and the request ignored

v2.7.3

Typing a { will no longer cause code completion to automatically appear unless it was immediately preceded by a $

v2.7.2

This version contains no functional changes but updates some internal references to the extension’s publisher ID which has been changed from DanTup to Dart-Code.

v2.7.1

Further improvements have been made to reduce the chances of printing JSON from Flutter apps from crashing the debugger
If during a hot reload, code that has changed was not re-executed (for example if you change the main method) you will now see a notification with an option to perform a hot restart
Long Dart SDK version numbers (git hashes) will now be truncated in the status bar (the full version is available in the tooltip)

v2.7.0

When debugging, call stacks on Windows should no longer show long (incorrect) relative paths
Find references will no longer hang with Loading... if invoked somewhere that has no results (eg. keywords)
Code completion will no longer hang with Loading... when using the Angular plugin and there are no results
Code completion will now trigger automatically after typing $ or { inside strings
Saving pubspec.yaml in a Flutter project will no longer run pub get but instead run the Flutter eqvuilent
Executing SDK commands will now pick a more appropriate workspace (or prompt for one if it cannot)
Folders named packages that contain real projects (like inside the Flutter repo) will now be detected more accurately (reducing package path resolution issues)
The Flutter debugger will no longer crash if you print a JSON array
The Flutter debugger will no longer hang if you create breakpoinst prior to launching the debug session
Vanilla Flutter projects inside the Fuchsia tree should now be treated like Flutter and not Fuchsia, enabling the Flutter deamon and debugging support

v2.6.2

An issue with pub and flutter commands not working from the command palette (introduced in v2.6.0) has been fixed

v2.6.1

The error message displayed when the analysis server cannot be found is more useful (previously it incorrectly reported that it had terminated)
An issue where the analysis server was not found if the dart executable in your PATH is a symlink (introduced in v2.6.0) has been fixed

v2.6.0

Note: This version requires Visual Studio Code 1.18.

Multi-root support

VS Code 1.18 gained support for multi-root workspaces, which allows multiple folders to opened at the same time. Perviously, much of Dart Code’s functionality would just act on the first folder in the list. Now, all functionality should work as you would expect.

When adding a Flutter or Fuchsia project to a multi-root workspace that didn’t previously have one, you will be prompted to reload to allow switching to the correct SDK
When running Flutter/Pub commands with multiple projects open, you will be prompted to select which folder to execute them for
Several settings have been promoted to resource-level which allows them to be set at a folder level even inside a multi-root workspace:
- dart.insertArgumentPlaceholders
- dart.lineLength
- dart.pubAdditionalArgs
- dart.runPubGetOnPubspecChanges
- dart.flutterRunLogFile
- dart.debugSdkLibraries
- dart.debugExternalLibraries
- dart.observatoryLogFile
Settings not listed above as resource-level must now be set at a User or Workspace level (VS Code will highlight such settings if you set them at a folder level)
The Dependency tree is hidden when you are working in a multi-rook workspace

Other Changes

SDK search paths have been simplified to make them easy to understand when trying to diagnose missing SDK issues
The dart.sdkContainer setting has been renamed to dart.sdkPaths and an array of multiple paths (this allows you to list several SDKs or folders full of SDKs can quickly switch between them using the SDK Version in the status bar)
The SDK Version switcher is now available for Flutter and Fuchsia projects
A new setting has been added to override the Flutter SDK location (dart.flutterSdkPath)
SDK overrides now apply to all project type (Fuchsia, Flutter, Dart)
The depdency tree will no longer appear in the explorer pane when there are no dependencies to show

v2.5.1

Chinese characters in paths should no longer result in breakpoints not being hit during debugging

v2.5.0

A new Dart: Open Observatory command is now available during Dart and Flutter debugging sessions to launch Observatory in a browser
A new Dart: Open Timeline command is now available during Flutter debugging sessions to launch the Observatory Timeline in a browser
Closing Labels are now enabled by default when you are using a version of the SDK that supports it
- A new option (dart.closingLabels) has been added to allow these to be disabled
The setting dart.flutterHotReloadOnSave now defaults to true and will force a hot reload upon saving (if there are no errors in the file being saved)
Progress messages will now be shown in the status bar when building/debugging Flutter projects
Characters typed at the end of a line will no longer appear after the Closing Labels
The dart.sdkContainer option (which adds a quick “SDK Picker”) now works if pointing directly at an SDK instead of its parent

v2.4.4

The search path for the Flutter SDK cached by Fuchsia has been updated in line with the latest Fuchsia code
The dart.userDefinedSdkPath setting will now override the Dart SDK used for Fuchsia projects (this is temporary until Fuchsia and Flutter get their own override)

v2.4.3

Note: This version requires Visual Studio Code 1.17.

The search path for the Dart SDK in Fuchsia projects has been updated to reflect the new location in a third_party folder
Several debug APIs are being removed in Code 1.18 so Dart Code has been moved off them - these should have no visible effects but since there was a lot of refactoring there is risk of new bugs in:
- Code that provides debug configurations for new projects that do not have a .vscode/launch.json file
- Code that supplements the launch config with things like SDK paths before passing to the debug adapter
- Code that passes custom commands (like Flutter’s hot reload, toggle debug painting, etc.) from the IDE to the debug adapter

v2.4.2

The Closing Labels preview feature will no longer show a toast popup asking for feedback every time it activates

v2.4.1

Note: This version requires Visual Studio Code 1.16.

Tooltips for items with no dartdocs will now appear correctly (a breaking change in Code 1.16 resulted in these disappearing)
The text color for Closing Labels preview can now be controlled using the dart.closingLabels color (you can set this in your settings, inside the workbench.colorCustomizations section - see here)
Go-to-Definition will no longer sometimes open some files inside your own project as read-only on Windows because of path casing differences
TODOs will now appear with lower priority than lints and hints in the Problems pane
The error message shown when the Flutter SDK cannot be find will now correctly refer to the FLUTTER_ROOT environment variable instead of FLUTTER_HOME

v2.4.0

Dart Code will now activate if a workspace contains a .dart file rather than only if it contains a pubspec.yaml file or when a .dart file is specifically opened
The dependency tree should work more reliably for .packages files that are not consistent with those generated by pub (for example, the hand-maintaned one in the Dart SDK repo)
Errors that occur when running Flutter debug commands will now be shown in the debug console
The Closing Labels preview has been updated to use functionality provided by the Dart SDK which will result in better performance and improved labels (this requires SDK v1.25.0-dev.11.0 or later)

v2.3.5

When working with a project that does not have trailing slashes on paths in the .packages file (such as dart-lang/sdk) breakpoints in packages should now work as expected.

v2.3.4

Go-to-Definition now works in read-only files (eg. SDK or external files opened using Go-to-Definition)

New Preview Features available in this version

dart.previewAnalyzeAngularTemplates - Enables analysis for AngularDart templates (requires the angular_analyzer_plugin)

v2.3.3

The dependency tree will now update after packages are changed/updated
When opening a Fuchsia project, the explorer will no longer indefinitely show a progress bar caused by trying to read dependencies
When using Go to Definition, files that are outside of your workspace root (eg. packages, SDK sources) will now be readonly to avoid accidental modification

v2.3.2

A new “Packages Tree” has been added to the explorer which lists your projects depencies and allows you to browse them in a read-only view
The ability to switch SDKs has been removed for Flutter and Fuchsia projects where it does not make sense
Fuchsia projects are now detected and will use the correct Dart SDK from Fuchsia
The dart.previewFlutterCloseTagDecorations preview feature has had several improvements
- Decorations now appear in Fuchsia projects as well as Flutter projects
- Decorations now appear for any Widget-returning method instead of only methods named build
- Decorations will update less frequently to avoid flickering during quick typing
- Decorations should no longer appear in invalid places (probably)
- Decorations now look more like comments, prefixed with // instead of /
- Decorations now apply to const constructor calls as well as those using new

v2.3.1

An issue with searching symbols in a file being unreliable (appearing to hang) has been fixed
A new setting flutterHotReloadOnSave has been added to force a hot reload upon saving (if there are no errors in the file being saved)
A new Flutter: Hot Restart command is now available during Flutter debugging sessions

New Preview Features available in this version

dart.previewFlutterCloseTagDecorations - Show annotations against Flutter widget constructor calls that span multiple lines

v2.3.0 - Flutter Debugging Commands

Several new commands have been added to aid Flutter debugging. These appear in the command palette but can be bound to keys in the Keyboard Shortcuts window in Code.

Toggle Debug Painting
Toggle Performance Overlay
Toggle Slow Animations
Toggle Repaint Rainbow
Toggle Platform (Android/iOS)
Toggle Baseline Painting
Toggle Slow-Mode Banner

Additionally the default hotkey for Organize Directives has been removed to avoid a warning from Code about modifier keys. You can rebind this command in Code’s Keyboard Shortcuts window.

v2.2.0

When running on Mac OS + iOS breakpoints should work from first launch without having to hot reload first
A new Dart: Sort Members command has been added
The Debug: Start without Debugging command will no longer error if this is the first time running a project (where the .vscode\launch.json file does not exist)
A new setting sdkContainer has been added which can be used for fast SDK switching - set to a folder that contains multiple SDKs and the Dart SDK version in the status bar will become clickable

v2.1.0

[Flutter] A new command has been added to the command palette to run flutter doctor
Dart and Flutter SDKs are now found in PATH even when they start with ~/ for a users home directory
All path names in config (log files, analyzer path, SDK path) now support starting with ~/ for a users home directory
When enabled, debug logging should now flush correctly before terminating to reduce the changes of data not being recorded
A new setting has been introduced (showLintNames) which will prefix lint/hint names into messages in the Problems pane to make it easier to // ignore them if you wish

Note: If you previously installed a beta version of Dart Code to help with testing Flutter integration, please uninstall it and close all Code instances before installing v2.0 from the marketplace.

[Flutter] When opening a Flutter project your selected device will be shown in the status bar
[Flutter] If you have more than one connected device you will be able to switch between them by clicking on the device in the status bar
[Flutter] Pressing F5 will build and launch your app on the selected device
[Flutter] The usual debugging experience is available for Flutter apps, including breakpoints, call stacks, watch window etc.
[Flutter] The debugger’s Restart button (or Ctrl+Shift+F5) has been mapped to Flutter’s hot reload and will update the running application without needing to rebuild
[Flutter] Code completion for Widgets will no longer show trailing commas in the list (though they will still be inserted)
Clicking the debugger’s restart button for a Dart CLI app will no longer crash but instead provide a more useful message about being unable to restart when VS Code does not supply toe correct configuration (this issue is fixed for VS Code 1.14 coming soon)
Stack frame text when stopped in the debugger is now improved and will show async gaps
Cursor placement after code fixes and assists should now be more accurate

v1.4.2

Note: This version requires Visual Studio Code 1.13.

Code completion will now show types for named arguments more reliably
Argument placeholders will now (again) insert placeholder text instead of empty strings
Completing methods that take no arguments will no longer place the cursor between the parens as if there are arguments to type
When selecting items from the code completion list the cursor will now more reliably move to the expected location after insertion
New snippets have been added for test and group methods defined in the test package
Dart Code will now activate when opening workspaces that include a pubspec.yaml anywhere in the tree, not just in the workspace root folder
Debug logging will no longer appear in the Debug Output window when launching a debug session
Snippets now have slightly more verbose descriptions of their functionality

v1.4.1

Identifiers that start or end with $ symbols will now highlight correctly
Highlighting of variables inside interpolated strings is now more accurate
Configuration snippets have been added to make adding additional debug configs to launch.json easier

v1.4.0

Code assists are now available and will show up as lightbulbs similar to existing code fixes (for example, Wrap in new widget in Flutter projects)
Code completion will now refresh on certain key presses (space, (, =) which should result in more accurate results more often
Code completion results are now sorted by relevance rather than alphabetically
Cursor position should now be better maintained when executing code fixes
pubspec.yaml and analysisoptions.yaml will once again use the built-in YAML language/highlighting
When opening a flutter project, the .packages file will now also be used when trying to locate the Flutter SDK
The error message shown when unable to locate the Flutter SDK has been simplified and a link to the Flutter download page added
The environment variable FLUTTER_HOME is not recommended for use and will no longer be used to locate a Flutter SDK (FLUTTER_ROOT is still checked)

v1.3.0

When opening a Flutter project, the below locations will be checked for a Flutter SDK and the embedded Dart SDK will be used (if no flutter SDK is found an error message will be shown)
- .\bin\flutter(.bat)
- (FLUTTER_ROOT)\bin\flutter(.bat)
- All folders in PATH
Dart SDK update checks are now disabled for Flutter projects due to the embedded Dartk SDK
Pub commands are now generally replaced with Flutter equivalents when a Flutter project is open (note: Pub commands still appear in the command palette for familiarity but will execute flutters versions)
When flutter: sdk: flutter is added to/removed from pubspec.yaml you will be prompted to reload to switch between Dart/Flutter SDKs
Pub commands will no longer appear in the command palette when a Dart project is not open

v1.2.0

The change made in v1.1.0 to support opening the Flutter repo introduced some new issues and has been reverted except for specific workspaces. The issue is caused by using a folder named packages which is not currently supported by the analyzer. In order to fix the issue for the Flutter repo the workaround will be triggered by the presence of a .\packages\.gitignore file (which exists in the Flutter repo but not in packages folders created by pub). This workaround will be removed once the Analyzer has been updated.

v1.1.0

Opening a folder that is not itself a Dart package but contains others (such as the Flutter repository) will no longer give false errors/warnings caused by incorrect package resolution
Setting Dart SDK/libraries as debuggable/non-debuggable will now work correctly with SDK 1.23 which has different debugging defaults
The launch.json file should now be much simpler than before and not contain internal Dart Code settings that are not relevant to the user *
The launch.json file now properly supports default so checkedMode: true and args: [] are not longer required unless being changed *

* Your launch.json file should automatically be tidied up when you first open your project.

v1.0.2

interface has been removed from the list of keywords for syntax highlighting. It has not been a Dart keyword for sometime and resulted in incorrect coloring when using it as a variable name
Expressions in interpolated strings should now be highlighted even when containing properties and method calls

v1.0.1

Opening a Dart file from the Dart SDK (such as navigating via Go to Definition on an SDK type) when using a dev-version 1.23 Dart SDK will no longer result in an infinite analyzing loop causing Analyzing... to flicker on the status bar

v1.0.0

Pressing F5 to launch Dart programs after upgrading to Code 1.10 will no longer fail with an error about an unexpected token in launch.json
Pressing F5 to launch Dart programs will now use Dart’s checked mode by default
A new setting has been introduced (pubAdditionalArgs) that allows additional arguments to be passed to pub in the Pub: Get Packages and Pub: Upgrade Packages commands (this may be useful if you wish to use --packages-dir)
The order of items in error reports have been tweaked slightly to move more useful stuff further up

v0.15.1

Fixed an issue introduced in v0.15.0 where null would something appear in tooltips for items with no doc comments.

v0.15.0

Tooltips will now show include the name of the library that a type comes from.
When the Dart: Organize Directives command fails (eg. due to a compile error) the correct message will be displayed instead of [Object object]

v0.14.9

Completing named arguments that already have values will no longer cause the argument name to be inserted twice.

v0.14.8

An error message about the “new driver” will no longer appear when using version v1.22.0-dev.5.0 or later of the Dart SDK.

v0.14.7

Note: This version requires Visual Studio Code 1.8.

Code completion will no longer insert underscore characters after upgrading to Code 1.8.

v0.14.6

Using the experimental analysis driver will no longer result multiple error reports being offered when an error occurs

v0.14.5

Passing additional arguments to the analysis server via the hidden setting dart.analyzerAdditionalArgs now works as expected
Generated error reports will now include which analysis server arguments were used
Generated error reports will now include which type of request the server was processing
Generated error reports may now include additional diagnostic information from the analysis server
Generated error reports will now include some intro text encouraging the user to review the report for any sensitive information

v0.14.4

Some additional debugging settings have been added to help track down analysis server issues
Changing analysis server debug settings will now prompt you to reload the project to restart the analysis server
Some minor tweaks have been made to the error report generation when the analysis service crashes
Exception analytics should no longer sometimes include users source code paths/filenames in logs

v0.14.3

When changing the dart.sdkPath setting you will now be prompted (and given a button) to reload the project
If the analysis service crashes and analytics are enabled, the first line of the error message will be included in an analytics event

v0.14.2

Fix to fix for analytics :(
Add timings for extension activation and analysis server startup

v0.14.1

Minor update to improve session handling for analytics

v0.14.0

Note: Due to use of new APIs, Dart Code v0.14 requires Visual Studio Code v1.6 or newer.

Debug Just My Code

New settings have been added controlling whether to step into SDK and external library code when debugging. When first opening Dart Code with this change you will be prompted to choose whether to “Debug just my code” or “Debug all code”. You can change this at any time with the dart.debugSdkLibraries and dart.debugExternalLibraries settings.

Analysis Server Error Reporting

If the analysis server encounters an error you will now be prompted (up to 3 times per session) to report the issue to the Dart team. Clicking “Generate error report” will build a document of markdown that you can simple copy/paste directly into the Dart SDK issue tracker (linked at the top of the report).

Misc

A small change was made to ensure debugging compatibility with future versions of the Dart SDK.
If the Dart SDK is not found on your machine, the error message will now include a button to launch the Dart installation page.
As of Visual Studio Code v1.7, the editor.formatOnSave setting will work correctly for Dart files.

v0.13.1

Code completion should no longer occasionally fail showing Loading...
Invoking Go to Definition on import statements should no longer occasionally fail silently

v0.13.0

Support has been added to format documents while typing (you must enable editor.formatOnType). This currently triggers when you type ; or }. Please send feedback!

v0.12.0

A new “type hierarchy” feature has been added (F4)
The “Preview” tag has been removed from Dart Code
The VS Code version number is now included in analytics to help make decisions about when code supporting older versions of Code can be removed

v0.11.2

If the Dart analysis server crashes you will now be prompted to save and reload the project (rather than everything being silently broken)

v0.11.1

A new setting has been added (dart.insertArgumentPlaceholders) to turn off placeholder insertion during completion operations
More improvements have been made to hovers (these appear best in Code 1.6, currently the Insiders build)
Large lists will now be “paged” in the debugger locals/watch windows to improve performance
The SDK update notification now has a button to jump directly to the Dart SDK download page

v0.11.0

Code fixes have been added! Use Ctrl+. for the lightbulb menu or F8 for diagnostics widget
pub get will run automatically when you save pubspec.yaml (can be disabled with the dart.runPubGetOnPubspecChanges setting)
Completion for methods/constructors now adds placeholders for mandatory arguments
Completion for named arguments now adds a placeholder for the value
Pressing <ENTER> in a triple-slash comment (/// ...) will now pre-complete the comment markers for the next line
Pressing <ENTER> in an old-style multiline comment (/** ... */) will now pre-complete following lines and place the closing marker (*/) in the right position
Hovers will no longer contain hyperlinks that don’t work when docs reference other elements
Display improvements to hovers/tooltips (these are not finished and will continue to be improvedin future releases)
Completion now shows when an element is deprecated
Hovers will now show when an element is deprecated (note: requires Dart SDK 1.20, currently unreleased)

v0.10.0

Debug support has been added! Breakpoints, hover evaluation, watch window, call stack etc. should all work (with some minor known issues)
Rename (F2) now works for most items
The update check for SDKs now connects to the internet to check for updates instead of using a hard-coded last-known-update value
A new setting has been added to disable SDK update checks/notifications (dart.checkForSdkUpdates)
Properties will now display better in completion/symbol lists and not as callable methods
SDK paths that have been removed from settings will no longer continue to be searched at startup
Indent settings for pubspec.yaml and analysis_options.yaml will now also be forced into 2-spaces at load (if dart.setIndentation has not been set to false)

v0.9.0

A warning will be shown at startup if your Dart SDK is older than the one the current Dart Code was tested with
If you have multiple open Dart projects using different versions of the SDK, running a command line app (F5) will no longer use the SDK from the last Dart project opened
Various improvements have been made to the display of search results and code-completion items
Snippets have been added for common code (main, try, switch, import, class, typedef and more!)
Errors will no longer occur trying to run pub get or pub upgrade if your SDK is in a path that contains spaces

v0.8.2

The display of symbols in the workspace symbol search (Ctrl+T) has been improved *
The Dart language service will no longer crash when you enter symbols into the (Ctrl+T) search box
Pressing F5 will now allow you to run a Dart command line application (you will need to set the path in .vscode\launch.json) **
Organize Directives (ctrl+alt+o) has been added

v0.7.0

Workspace symbol search (Ctrl+T) now includes more symbols from your workspace including imported packages
Document symbol list/search has been implemented (Ctrl+Shift+O)
Document highlights have been implemented (selected a symbol will highlight other instances)
Commands for pub get and pub upgrade have been added
Errors and warnings from files that are deleted when not open will no longer hang around in the problems view

v0.6.2

Find References (Shift+F12) has been added
Open files are given higher priority for analysis operations
The extension no longer tries (and fails) to analyze open files that are outside of workspace folder

Additionally, a new option dart.allowAnalytics was added to control if analytics are sent. Only very basic events are captured (such as extension activation and if you toggle certain features) and are sent along with the extension version/platform. No code, filenames, project names or personal information will be sent. Source code for all analytics is visible here.

v0.6.1

A new setting dart.showTodos (default: true) has been added to show/hide TODO messages from the Problems list
“Analyzing…” will now show in the status bar when files are being analyzed
Go to Definition is now supported within your project (though does not yet work with SDK classes)
The Dart SDK version number will now show in the bottom right status bar
Dart files will automatically be set to 2-space indenting when you open them
A new setting dart.setIndentation (default: true) has been added to enable/disable automatic indent settings
Symbol search is now case-insensitive and also supports better filtering (eg. “TA” will match “TwitterApi”)
Tooltips reading undefined will no longer appear for some items (eg. string literals)
Tooltip formatting/display has been greatly improved

v0.5.2

SDK detection is more reliable on Linux/Mac
Name changed from “Dart-Code” to “Dart Code”
Setting added to control line-width passed to formatter
Last used SDK path is cached to improve startup performance
Tooltip hovers now indicate the range that they apply to
Braces/quotes now automatically close
Pressing enter between a set of braces will automatically indent

v0.1.0

Syntax highlighting
Code-completion
Diagnostics (errors/warnings/hints)
Workspace-wide symbol search
Reformatting document
Tooltips