Node.js 27 Alpha: V8 15.6 Doubles Default Heap Limit, Breaks Serialization Compatibility

Release Cadence and V8 Upgrade

On October 29, Node.js released its first 27 Alpha preview, version 27.0.0-alpha.0.0. Starting with this version, Node.js switches to a yearly major release in April, dropping the even/odd LTS distinction; Node.js 27 will become LTS in October 2025. The core change is the V8 engine upgrade from 14.6 (in Node.js 26) to 15.6.

Default Heap Limit Doubles on 8 GB Machines

Previously, on machines with 4–15 GB of memory, V8's default old-generation heap limit was half of physical memory, capped at 2 GB. V8 15.6 changes this to half of physical or cgroup memory, clamped between 256 MB and 4 GB. Consequently:

6 GB machine: default limit rises from 2 GB to 3 GB.

8 GB machine: default limit doubles from 2 GB to 4 GB.

Container workloads that relied on the implicit 2 GB ceiling will see old-generation memory consumption double unless --max-old-space-size is explicitly configured.

Additionally, off-heap Buffer and ArrayBuffer allocations are now counted toward V8's global allocation limit, altering GC trigger timing for services that frequently allocate large binary buffers.

High-frequency Worker thread creation incurs extra overhead: each native handle wrapper adds ~16 bytes on-heap and ~50 bytes off-heap; each isolate (per Worker) adds ~180 KB for property lookup caches. On the positive side, worst-case GC pause drops from ~45 ms to ~10 ms in benchmarks; Error stack traces are now lazily constructed only when error.stack is accessed; unused function bytecode is cleaned up after ~3 minutes of inactivity.

Serialization Format Change Breaks Cross-Version Compatibility

V8 15.6 enables a new serialization format. structuredClone() and postMessage() can now transfer TypedArrays and resizable ArrayBuffer s larger than 4 GB (though v8.serialize() retains a 4 GB limit). New runtimes can read old serialized data, but old Node.js versions reading data serialized by Node.js 27 throw "invalid or unsupported version". Rolling upgrades with mixed-version serialization payloads must isolate traffic.

Heap Snapshot Size and Content Changes

Generating a heap snapshot in Node.js 27 takes roughly twice as long and produces files twice as large. Snapshots no longer truncate script text; they include full source code and scope-captured variables to support new DevTools features for detecting unused variables. This increases risk if production snapshots contain sensitive literals. Global objects are now named global [JSGlobalObject] and global [JSGlobalProxy] in snapshots, requiring tooling updates.

Behavioral Changes Affecting Tests

Some Math methods now use LLVM's libm, causing tiny last-bit floating-point differences for certain inputs. Math.random() sequences differ from Node.js 26 when --random-seed is specified.

Large-array Array.prototype.sort() switches to the PowerSort algorithm. error.stack no longer walks the prototype chain.

New Developer-Facing Features

Precise summation: Math.sumPrecise() reduces floating-point error accumulation when summing arrays.

Iterator combinators: Iterator.zip(), Iterator.zipKeyed(), and chainable join() and includes() methods allow composition without intermediate arrays.

// Reduce floating-point accumulation error
Math.sumPrecise([0.1, 0.2, 0.3]); // 0.6

// Iterator chaining for join and pairing
[1, 2, 3].values().map(x => x * 2).join('-'); // '2-4-6'

Iterator.zip([[1, 2], ['a', 'b']]).toArray(); // [[1, 'a'], [2, 'b']]

Iterator.zipKeyed({ id: [1, 2], name: ['a', 'b'] }).toArray();
// [{ id: 1, name: 'a' }, { id: 2, name: 'b' }]

Performance Improvements

Repeated BigInt modulo with the same divisor: ~25% faster (measured in bigint-noble-ed25519), benefiting pure-JS cryptography.

Property access on objects with many properties or deleted properties: ~10% faster in richards, ~20% in espree-wtb.

Async generators: ~6% faster in async-fs.

Regular expressions now compile to machine code on first use; hot regexes run faster, one-off regexes pay a compilation cost. JSON.parse speeds up for inputs with many strings or homogeneous object arrays.

Upgrade Timeline and Recommendations

Alpha phase runs until April 2025, then Current, then LTS in October 2025. V8 may continue major upgrades; native addon ABI changes will increment NODE_MODULE_VERSION. Maintainers of open-source libraries or native addons should add 27.0.0-alpha to CI now to catch the memory and behavioral changes early.