For instructions on installing the Dart or Flutter extensions, go here.
v3.68.1 2023-07-04
- #4625: The new warning about invalid SDK paths in config will no longer appear when your SDK is a symbolic link.
v3.68.0 2023-07-03
Automatically Clone Flutter SDK
#4532: When no suitable Flutter SDK is found, the “Download SDK” button will now attempt to use Git to clone an SDK before launching the Download page from the Flutter website. You will be prompted for a location to download the SDK to and the path will automatically be written into the dart.flutterSdkPath setting.
Add Dart/Flutter SDK to PATH Environment Variable
#4604: New commands Add Dart SDK to PATH / Add Flutter SDK to PATH will attempt to add your current SDK to the PATH environment variable automatically. This is currently only supported on Windows, but other platforms will provide a link to additional information. You’ll be prompted for this automatically if you use the Clone Flutter SDK flow noted above.
Editor
- #4615: The textmate grammar for basic syntax highlighting has been updated to v1.2.2.
- #4384: Test icons in the gutter are no longer duplicated when pressing
<enter>in the first line of a test definition. - #4608: A warning will now be shown if
dart.sdkPath/dart.flutterSdkPathare configured but do not resolve to a valid SDK.
Commands
- #4606: The Dart: New Project and Flutter: New Project input boxes no longer close automatically if focus is lost. This allows you to tab away (for example to copy/paste values) without having to start over. Pressing
<escape>will still cancel project creation. - #4581: Folders that contain
__or\{\{are now excluded from automaticpub getchecks, since these are often template directories and not valid projects.
Testing
- #4602: Formatting of Flutter error messages in the Test Error popup has been fixed.
- #4594: Expanding a test file in the test explorer tree that is not open will no longer often fail to discover tests in that file.
- #4553: The “Run All Tests” action handles excluded suites better and now produces shorter command lines (reducing the chance of “Command line too long” on Windows).
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 in future. If you’re using a recent bleeding-edge version, these items should already be available to you and any issues should be reported on GitHub in the usual way.
All of these issues relate to using the new SDK debug adapters that are being gradually rolled out:
- #4599: Breakpoints in a file will no longer sometimes be left “unverified” when adding/removing other breakpoints in that file.
- #4420: The debug adapter now drops references to variables, scopes and stack frames when execution resumes to reduce memory usage over long debug sessions.
- #4287: Running Dart CLI apps using
cliConsole=terminalwill no longer show the terminal and then switch back to the Debug Console when the app launches. - #4505: Skipped tests no longer show ticks which made them look like passing tests.
- #4542: Triggering a hot reload during application launch will no longer report “DebugAdapterException: app ‘null’ not found”.
- #4577: The Flutter debug adapter now supports the
vmServiceInfoFilefield which is useful for attaching debug sessions to Flutter instances started by other tools that can produce this file. - #4597: The pause action is now available.
Upstream Issues
Some feature requests and fixes require new features and fixes in upstream projects like VS Code and LSP which use counts of 👍s on those issues to help gauge demand. The Dart-Code website now lists some of the most significant upstream issues with a description of the feature/fix they would enable. Please consider reviewing this list and adding your 👍 to any GitHub issues relevant to features you’d like to see!