deno temporal-api nodejs-compat windows-arm release

Deno 2.7 stabilizes Temporal, adds Windows ARM builds

Temporal API moves out of unstable, Windows ARM gets native support, and subprocess spawning gets simpler APIs—but spawn functions still unstable.

Summary

Temporal is now production-ready without flags, ARM Windows developers eliminate emulation overhead, and Node.js compatibility fixes (worker threads, child_process, zlib) make migrating Node projects to Deno more viable.

Why it matters

Implementation verdict

Temporal replaces hand-rolled date arithmetic and timezone logic; spawn() functions replace Deno.Command() for simple cases but remain unstable—try now for dates, wait on spawn APIs until stabilized. Requires deno upgrade to 2.7.

Sources

1.The Temporal API is now stable in Deno. The --unstable-temporal flag is no longer required.
2.Deno now provides official builds for Windows on ARM (aarch64-pc-windows-msvc)
3.The new Deno.spawn(), Deno.spawnAndWait(), and Deno.spawnAndWaitSync() functions are convenient shorthands for the existing Deno.Command API
4.These new APIs are currently marked as unstable, meaning that they may evolve over time until formally stabilised in the runtime.

Dev Signal

Get briefs like this in your inbox — free, 3x a week.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs