Dev Tools

Node.js 27 alpha lands V8 15.6 with new memory defaults

The first Node.js 27 alpha brings V8 15.6, a new heap-size default, incompatible serialization and several semver-major runtime changes.

By CodeYourVibe Editorial · 06 November 2026

Editorial cover for the news story: V8 15.6 lands with new memory defaults — Editorial cover built around an official brand mark. Story source.

What Changed

Node.js 27.0.0-alpha.0.0.0 was published on 29 October 2026. It updates V8 to 15.6.75.13 and enables Math.sumPrecise, Intl.Locale variants, and several Iterator helpers by default. When --max-old-space-size is not set, the default heap limit is now half of physical memory clamped between 256 MB and 4 GB, and Buffer/ArrayBuffer memory counts toward the heap limit. v8.serialize, structuredClone and postMessage use a new format that older Node.js releases cannot read. The release also requires OpenSSL 3, removes the bundled FIPS provider, adds native fs.glob, changes HTTP header handling, and makes many semver-major changes.

Why It Matters

This is an alpha, but the changes surface real upgrade risks early. Services that relied on V8's previous default heap can hit different memory behaviour, and anything that persists serialized objects across Node versions may fail to read them. Native addons and crypto code face OpenSSL and API removals. Testing now, while the release is still alpha, is cheaper than discovering these issues during a later major upgrade.

Practical Impact

Do not deploy Node 27 alpha to production. Add a CI job that runs the alpha against your test suite, with an explicit --max-old-space-size so memory results are comparable. Exercise worker threads, child processes, caches and anything that stores v8.serialize output; do not assume old cached data is readable. Rebuild native modules against OpenSSL 3. Read the semver-major list before planning an upgrade, and report regressions with minimal reproductions while the release is still fluid.