# Node.js 26 enables Temporal by default in its Current release > Node.js 26 ships Temporal, a newer V8 engine, and removals of legacy APIs, giving maintainers a concrete compatibility target before its planned LTS phase. Canonical URL: https://www.devobs.io/news/news-node-26-temporal-current/ By: Claire Dubois Published: 2026-09-06T11:58:54.643Z Updated: 2026-09-06T11:58:54.643Z Event date: 2026-05-05 Section: Languages Node.js released version 26.0.0 on May 5 as its new Current release. The [release notes](https://nodejs.org/en/blog/release/v26.0.0) enable Temporal by default, update V8 to 14.6, and describe several removals that make this more than a routine engine refresh. ## Date and time gain a new option Temporal is available without an enabling flag. The release also updates the Undici HTTP client and removes legacy stream modules and the experimental TypeScript transformation flag. At launch, the project described an October transition to long-term support. For application owners, the immediate value is a defined compatibility target. Run the runtime upgrade independently of a large date-handling rewrite. Otherwise, failures caused by a removed API can become entangled with changed application logic, making both harder to evaluate. ## Map the upgrade to real usage A Temporal experiment should start with a narrow domain question: does the application mean an instant, a local calendar date, or a scheduled time in a particular zone? Put representative boundary cases beside the existing behavior before replacing a widely used helper. The new API provides vocabulary; the application still has to choose its intended semantics. Meanwhile, inspect startup options and dependency usage for the removed surfaces. A library can invoke an old module even when the application's own source never mentions it, so a text search alone is incomplete. Use a representative deployment artifact for the compatibility run, including its launch configuration. The resulting report should separate runtime adoption blockers from optional feature work. That lets teams prepare for the release line without making every new capability a prerequisite for upgrading. ## Source references -