Dart 3.14 Adds dart migrate and Hardware WebAssembly SIMD and Marks FFIgen for Objective-C and JNIgen Stable; Its Changelog Lists Breaking Changes
Dart's blog post dated November 11 lists dart migrate, WebAssembly SIMD and stable FFIgen for Objective-C and JNIgen; the 3.14.0 changelog also lists breaking changes to SIMD types and unshipped Isolate APIs.
Overview
The Dart team published a blog post dated November 11, 2026 announcing Dart 3.14. The post, Announcing Dart 3.14 by Connie Ooi, lists a new dart migrate command, a beta of a re-engineered DartPad, hardware 128-bit WebAssembly SIMD in the dart2wasm compiler, and FFIgen for Objective-C and JNIgen as stable. The 3.14.0 changelog on GitHub also contains, by the Herald’s count, three entries labelled “Breaking change”, two for the SIMD types in dart:typed_data and one for dart:isolate. A text search of the announcement by the Herald found none of the three mentioned. A companion post, What’s new in Flutter 3.50, carries the same date.
What the announcement lists
dart migrate. The announcement says the tool automates upgrades by bumping a package “forward one version at a time”. Dart’s documentation says it supports projects whose minimum SDK constraint requires Dart 3.0 or later and does not upgrade the SDK installed on the machine. Because it “doesn’t check for uncommitted changes in version control”, the documentation advises committing or stashing work before running dart migrate --apply. The same page says cleanup fixes are listed in the summary rather than applied by default, and that the command does not automatically expand pub workspaces.
WebAssembly. According to the announcement, dart2wasm now compiles Int32x4, Float32x4, Float64x2 and their typed-data list views to hardware SIMD (v128) instructions, “delivering up to 4x speedups across native and WebAssembly SIMD benchmarks”. These are Dart’s figures, and the post does not name the benchmarks. The post also says the compiler now emits finalized try_table exception-handling instructions by default, which it says lets dart compile wasm --standalone output run in runtimes such as Wasmtime without a JavaScript host.
Package and tooling changes. The announcement says dart pub now stores the server’s ETag with cached package listings. Dart’s own example is a Flutter project with 144 dependencies, where the post says the change eliminates about 1.5 MB of repeated downloads. It also says the DartPad beta is built on package:dartpad, which compiles the Dart compiler, the analyzer and the pub client to WebAssembly and runs them locally in a Web Worker.
Native interop. The announcement says FFIgen for Objective-C and JNIgen are stable. The Flutter post adds that they “join FFIgen’s long-standing C support as stable”.
Legacy web libraries. The announcement says dart:html, dart:js, dart:js_util, package:js and related browser libraries are deprecated and “scheduled for removal from the Dart SDK in an upcoming release”. The Flutter post says they “will be removed in a future Dart release”. Neither post gives a version or a date. The changelog lists a --no-deprecated-js-interop flag for dart compile js and the development compiler that rejects imports of dart:html, dart:html_common, dart:indexed_db, dart:js, dart:js_util, dart:svg, dart:web_audio and dart:web_gl.
What the changelog adds
The changelog labels three entries “Breaking change”:
- SIMD
toString(). OnFloat32x4,Int32x4andFloat64x2,toString()now returns'V128'instead of the lane values. The entry says the old output “was inconsistent across platforms and was never specified”. - SIMD
minandmax.Float32x4.min,Float32x4.max,Float64x2.minandFloat64x2.maxnow follow IEEE 754 semantics: if either lane is NaN the result lane is NaN, and-0.0is ordered below+0.0. In issue #63962, whose reporter proposed the change, the reporter wrote that “it seems very unlikely that anyone depends on the exact NaN / signed-zero result” and that every backend could then use the native min and max instructions. - Isolate APIs. The entry says the release unshipped experimental synchronous execution and event-loop control APIs, among them
Isolate.runSyncandIsolate.runEventLoopSync, “that were accidentally exposed in Dart 3.13”, and gatedNativeCallable.isolateGroupBoundbehind the--experimental-shared-dataVM flag. The 3.13.0 changelog entry fordart:isolatebegins “Added synchronous execution and event loop control APIs” and, by the Herald’s count, names the same eight APIs. In issue #64285, opened on September 15 by the account mraleph, the author wrote that “we by accident shipped experimental Isolate and FFI apis” into the stable channel. The issue was still open when the Herald checked on November 15.
Among other entries not labelled breaking, the changelog says dart:mirrors is now deprecated and will be removed in a future release, that on Mac Process spawning moved to posix_spawn so that PATH is resolved from the parent, and that dart compile wasm --standalone no longer supports dart:js_interop.
Dates and browser floors
The Herald read the dates as follows. The commit “Version 3.14.0” (“Merge 3.14.0-315.3.beta into stable”) is dated 2026-11-04 16:28 in UTC-08:00, which is 2026-11-05 00:28 UTC. The 3.14.0 tag page shows 2026-11-11 08:24:12 UTC, about six days later by the Herald’s calculation. The migrate documentation says it was last updated on 2026-11-04, and the WebAssembly documentation says 2026-11-10. The changelog entry at the tag still reads “Released on: Unreleased”. The cited pages do not say when the SDK became downloadable.
The announcement names Chrome 137+, Safari 26.2+ and Firefox 147+ for WebAssembly. Dart’s WebAssembly documentation lists Chrome or Edge 137+, Safari 26.2+ and “Firefox 134+ (or 147+ for Flutter web)”, so the documentation puts the general Firefox floor at 134 and applies 147 to Flutter web, while the announcement gives 147 without that qualifier. The cited pages do not say why. The Flutter post says Safari 26.2+ and Firefox 147+ can be opted into today, before they become enabled by default in a future stable release. MDN’s browser-compat-data repository, pinned to a November 13 commit, lists JS String Builtins from Chrome 130, Firefox 134 and Safari 26.2, and exnref exception handling from Chrome 137, Firefox 131 and Safari 18.4. In the Herald’s comparison, for each of those three browsers the later of the two versions equals the floor in the Dart documentation (Chrome 137, Firefox 134, Safari 26.2).
What the sources do not settle
- Apart from the MDN data, every cited page comes from the Dart and Flutter projects’ own sites and repository. The Herald found and cites no outside report of the release, the DartPad beta or the performance figures, and it did not run
dart migrateor DartPad. - No cited page gives a version or date for removing the legacy web libraries.
- The announcement does not name the benchmarks behind “up to 4x”.
- The cited pages do not say whether the Isolate unshipping was backported to Dart 3.13; the entries for 3.13.1 to 3.13.7 in the changelog do not mention it.