|
| 1 | +--- |
| 2 | +title: v3.130 |
| 3 | +sort_order: v0003_0130 |
| 4 | +excerpt: "Testing improvements, performance improvements, bug fixes..." |
| 5 | +--- |
| 6 | + |
| 7 | +# v3.130.0 _2026-03-03_ |
| 8 | + |
| 9 | +## Testing |
| 10 | + |
| 11 | +- [#5904](https://github.com/Dart-Code/Dart-Code/issues/5904), [#5932](https://github.com/Dart-Code/Dart-Code/issues/5932), [#5928](https://github.com/Dart-Code/Dart-Code/issues/5928): Tests are now marked as queued when starting a test debug session. |
| 12 | +- [#5930](https://github.com/Dart-Code/Dart-Code/issues/5930): Running tests no longer sometimes cause "Cannot read properties of null (reading 'startsWith')" errors in the console and tests not to show up in the Test Results pane. |
| 13 | +- [#5934](https://github.com/Dart-Code/Dart-Code/issues/5934)/[#5937](https://github.com/Dart-Code/Dart-Code/issues/5937): Test discovery is now much faster in large projects, particularly when disk access may be slowed by antivirus scanning. |
| 14 | +- [#5935](https://github.com/Dart-Code/Dart-Code/issues/5935): `package:test` version detection (used to enable features like coverage) no longer fails if `dart run test:test --version` produces additional output (such as package fetching). |
| 15 | +- [#5949](https://github.com/Dart-Code/Dart-Code/issues/5949): Test suites no longer sometimes show up as if they are skipped tests in the Test Results pane. |
| 16 | +- [#5902](https://github.com/Dart-Code/Dart-Code/issues/5902): Tests that use `package:test_reflective_loader` are now grouped in the test runner by class (requires `package:test_reflective_loader` v0.6.0). |
| 17 | + |
| 18 | +## Editor |
| 19 | + |
| 20 | +- [#5894](https://github.com/Dart-Code/Dart-Code/issues/5894)/[#5896](https://github.com/Dart-Code/Dart-Code/issues/5896): The **Go to Imports** action no longer targets a different editor/group if the target file is already open elsewhere. |
| 21 | +- [#5913](https://github.com/Dart-Code/Dart-Code/issues/5913)/[#5914](https://github.com/Dart-Code/Dart-Code/issues/5914): The **Add Dependency** fix now correctly appears to move a dependency from `dev_dependencies` to `dependencies` when used in public files. |
| 22 | +- [#5918](https://github.com/Dart-Code/Dart-Code/issues/5918): Highlighting of `new` and `factory` is now consistent between the textmate grammar used for intial syntax highlighting and semantic tokens that are laid on top. |
| 23 | +- [#5920](https://github.com/Dart-Code/Dart-Code/issues/5920): The textmate grammar has been updated for the upcoming Primary Constructors feature. |
| 24 | +- [#5135](https://github.com/Dart-Code/Dart-Code/issues/5135): Various changes have been made to make the display of getters and field more accurate. Many places that would previously fields will now correctly show the implicit getters they produce. |
| 25 | + |
| 26 | +## Flutter |
| 27 | + |
| 28 | +- [#5948](https://github.com/Dart-Code/Dart-Code/issues/5948): Requests for emulators/platforms are no longer sent to the Flutter device daemon before device management is enabled. This might reduce the frequency of [timeouts of those requests](https://github.com/Dart-Code/Dart-Code/issues/5793). |
| 29 | + |
| 30 | +## Commands |
| 31 | + |
| 32 | +- [#5907](https://github.com/Dart-Code/Dart-Code/issues/5907)/[#5908](https://github.com/Dart-Code/Dart-Code/issues/5908): Pub commands like **Get Packages for All Projects** will now run multiple fetches in parallel, up to half the number of processors on the machine. |
| 33 | + |
| 34 | +## Misc |
| 35 | + |
| 36 | +- [#5909](https://github.com/Dart-Code/Dart-Code/issues/5909)/[#5910](https://github.com/Dart-Code/Dart-Code/issues/5910): Extension startup no longer fails if `.dart_tool/package_config.json` contains invalid file paths for the current platform (for example because it was copied/cloned from another platform). |
| 37 | +- [#5906](https://github.com/Dart-Code/Dart-Code/issues/5906): Extension activation no longer fails on `realpathSync.native` with some kinds of mounted drives. |
| 38 | +- [#5911](https://github.com/Dart-Code/Dart-Code/issues/5911): Support for SDKs prior to Dart 3.2 / Flutter 3.16 (which previously produced a warning about being deprecated) has been removed. A table showing which extension versions support which SDKs (and instructions on how to change extension version) is available on the [SDK Compatibility page](/sdk-version-compatibility/) if you need to continue to use an unsupported SDK. |
| 39 | +- [#5924](https://github.com/Dart-Code/Dart-Code/issues/5924): Some CI bots have been enabled to run Dart-Code's automated tests against Antigravity. |
| 40 | + |
| 41 | +## Features/Fixes Enabled with Future SDKs |
| 42 | + |
| 43 | +The following items depend on changes to the Dart/Flutter SDKs that have not yet been released to stable channels. They may be available to test in the current beta/master channels and will show up in future SDK releases. |
| 44 | + |
| 45 | +- [#5933](https://github.com/Dart-Code/Dart-Code/issues/5933): Stack traces are now shown in the exception popups when the stack trace might not be the same as where the debugger is paused (for example when errors are rethrown or `Completer.completeError()` is used). |
| 46 | +- [#5919](https://github.com/Dart-Code/Dart-Code/issues/5919): Factory constructors no longer sometimes appear as "<unknown>" in the breadcrumb/outline. |
| 47 | + |
0 commit comments