Node.js 26.0.0: Temporal API Enabled, V8 14.6 Upgrades, End of Old Versioning

Node.js 26.0.0 was released on May 5, with Rafael Gonzaga announcing key changes: the Temporal API is enabled by default, V8 upgraded to 14.6, Undici to 8, and continued deprecation work.

Temporal API default enabled, say goodbye to Date

The new default activation of the TC39 Temporal API lets developers avoid the long‑standing problems of the built‑in Date object (zero‑based months, timezone confusion, mutability). Previously it required the --experimental-temporal flag; now Temporal.Now.plainDateISO() works out‑of‑the‑box. Browser support is still pending, so the change mainly benefits pure Node.js back‑end code.

// Old Date usage
const d = new Date(2026, 4, 6);
// Temporal usage
const date = Temporal.PlainDate.from('2026-05-06');
const next = date.add({ days: 30 });
const zoned = Temporal.ZonedDateTime.from('2026-05-06T10:00[Asia/Shanghai]');

V8 14.6 brings useful language features

V8 14.6 (based on Chromium 146) adds proposals such as Map/WeakMap upsert and Iterator.concat. The upsert proposal replaces the common “get‑or‑insert” boilerplate:

// Before
let value = map.get(key);
if (value === undefined) {
  value = createValue();
  map.set(key, value);
}

// After
const value = map.getOrInsertComputed(key, createValue);

Iterator.concat allows concatenating multiple iterators into one:

const merged = Iterator.concat(iterA, iterB, iterC);
for (const item of merged) {
  // consume items from all iterators in order
}

A security fix (CVE‑2026‑21717) for V8 array‑index hash collisions is also included.

Undici 8 modernizes the built‑in HTTP client

Node.js’s built‑in fetch, Request, and Response now rely on Undici 8, which brings HTTP/2 handling, revised connection‑pool strategies, and updated error objects. Projects that import undici directly should review the changelog for potential breaking changes, while most code using the native fetch API benefits automatically.

Significant deprecations and cleanup

http.Server.prototype.writeHeader()

(a misspelling) has been removed; use writeHead() instead.

The legacy _stream_* modules are dropped in favor of the modern Stream API.

The --experimental-transform-types flag is gone; TypeScript transformation remains via other mechanisms.

Runtime deprecations now emit warnings for module.register(), Stream DEP0201, and Crypto DEP0203/DEP0204.

Platform support gains and losses

Node.js 26 adds support for Power 9 (AIX/IBM i) and enables V8’s Maglev JIT on Linux s390x, improving performance on those architectures.

Versioning transition: from 26 to 27

Version 26 is the last major release under the old “even‑numbered LTS” scheme. Starting with 27, releases will align with the calendar year (one major version per year, released in April, entering LTS in October, with a 36‑month support window). An Alpha channel will provide preview builds from October to March.

Upgrade recommendations

For production environments still on Node.js 22 or 24, migration to 26 can wait until it becomes LTS in October 2026. Library authors and early adopters may upgrade now, focusing on:

Removing usage of removed APIs such as writeHeader and _stream_*.

Ensuring direct dependencies on undici are compatible with 8.x.

Verifying the build toolchain meets the new GCC 13.2 requirement.

Evaluating Temporal API as a replacement for day‑js or date‑fns in suitable scenarios.

Conclusion

Node.js 26 is a “clean‑up and speed‑up” release rather than a radical overhaul. Temporal, V8 14.6, and Undici 8 provide modern capabilities, while the deprecation list prepares the project for the upcoming calendar‑aligned release cadence.