Skip to content
All articles
Node.jsNode.js 26LTSUpgrade

Node.js 26 LTS: What's New, What Breaks, and the New Release Schedule

Node.js 26 became LTS on 28 October 2026: Temporal by default, V8 14.6, what was removed since Node 24, support dates and the new yearly schedule.

Usama Munawar8 min read

The short version

Node.js 26 became the Active LTS line on 28 October 2026, with the codename Lithium. The promotion release, 26.13.0, contains no code changes from 26.12.1: it only marks the line as LTS, so everything below, written against the 26.12 builds, still applies.

What matters for backend and full-stack teams:

  • Temporal is enabled by default, so you get a proper date and time API without a polyfill.
  • V8 14.6 (Node 24 ships V8 13.6), with Map.prototype.getOrInsert() and Iterator.concat().
  • Removals across Node 25 and 26: the _stream_* modules, res.writeHeader(), fs.F_OK and friends, SlowBuffer, the --experimental-transform-types flag, and Corepack is no longer bundled.
  • Native addons need rebuilding: NODE_MODULE_VERSION is 147, up from 137 on Node 24.
  • Node 22 reaches end of life on 30 April 2027. That is the deadline that should drive your planning, not the 26 launch.
  • From Node 27, every release becomes LTS: one major a year, plus a new Alpha channel.

My advice: test on 26 now, move production after the LTS promotion and once your host supports it, and upgrade anything still on 22 first.

Support timeline

Dates from the Node.js Release schedule:

LineCodenameReleasedActive LTSMaintenanceEnd of life
22Jod24 April 202429 October 202421 October 202530 April 2027
24Krypton6 May 202528 October 202520 October 202630 April 2028
26Lithium5 May 202628 October 202620 October 202730 April 2029

Node 24 moved into maintenance on 20 October 2026; it keeps getting security fixes until April 2028 but fewer backports. Node 25 never became LTS and reached end of life on 1 June 2026. Node 20 reached end of life on 30 April 2026.

One more date: the project shipped security releases for the 26.x, 24.x and 22.x lines from 21 October 2026, with the highest severity rated HIGH (for example, TLS handling of non-canonical IP addresses). Whatever line you run, make sure you are on a build that includes those fixes. Node 26.13.0 does.

What is new since Node 24

Temporal, on by default

This is the change I care about most. Date is a common source of bugs in code that handles billing periods, bookings or time zones. Temporal separates the concepts Date mixes together (a calendar date, an exact instant, a date and time in a named zone), and its objects are immutable.

const start = Temporal.PlainDate.from('2026-10-28');
console.log(start.add({ months: 30 }).toString()); // 2029-04-28

const now = Temporal.Now.zonedDateTimeISO('Europe/London');
console.log(now.toString());

On Node 22 and 24, Temporal is not there by default (typeof Temporal is 'undefined'). If you publish a library or share code with older runtimes, keep a fallback or a polyfill until you drop them.

V8 14.6

Node 26 ships V8 14.6 (Chromium 146). Two additions I expect to use in ordinary backend code:

// Group jobs by tenant without the "if (!map.has(key))" dance
const byTenant = new Map();
for (const job of jobs) {
  byTenant.getOrInsertComputed(job.tenantId, () => []).push(job);
}

// Iterate several sources as one
for (const row of Iterator.concat(activeUsers, invitedUsers)) {
  sendDigest(row);
}

From the Node 25 release, which used V8 14.1, you also get built-in base64 and hex on Uint8Array (bytes.toBase64(), Uint8Array.fromBase64()), and the project highlighted faster JSON.stringify. I have not benchmarked that, so measure your own payloads before you credit it with anything.

Undici 8 behind fetch

Node 26.0.0 moved the built-in HTTP client, Undici, to version 8. Most code only touches it through fetch(). If you import undici directly, set custom dispatchers or agents, or pin an Undici version, read its release notes before upgrading.

TypeScript: strip-only

Type stripping has been on by default since 22.18 and 23.6, and is marked stable from 24.12 and 25.2. Node 26 removes --experimental-transform-types, so anything that needs code generation fails:

$ node --experimental-transform-types server.ts
node: bad option: --experimental-transform-types

$ node server.ts   # with an enum inside
SyntaxError [ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX]: TypeScript enum is not supported in strip-only mode

Enums, namespaces with runtime code and parameter properties need either a rewrite (a union type or a plain object) or a real compile step with tsc or a tool such as tsx.

Smaller changes

  • Web Storage came out from behind a flag in Node 25. On 26.12.0, localStorage is undefined and prints a warning unless you pass --localstorage-file. The API docs describe a DOMException instead, so do not build anything on either behaviour.
  • Permission model: Node 25 added --allow-net alongside the existing file system and child process permissions.
  • ErrorEvent is a global from Node 25.
  • npm stays on major version 11 (26.13.0 ships npm 11.20.0).

What breaks

These are the semver-major removals and deprecations between 24 and 26 that I would search a codebase for. Most are old APIs, so they tend to turn up in older dependencies rather than in your own code.

OldReplacementStatus
require('_stream_readable') and the other _stream_* modulesnode:streamRemoved in 26 (DEP0193)
res.writeHeader()res.writeHead()Removed in 26 (DEP0063)
fs.F_OK, fs.R_OK, fs.W_OK, fs.X_OKfs.constants.F_OK etc.Removed in 25 (DEP0176)
SlowBufferBuffer.allocUnsafeSlow()Removed in 25 (DEP0030)
Short AES-GCM auth tags without authTagLengthPass authTagLength to createDecipheriv()End of life in 26 (DEP0182)
module.register()module.registerHooks()Runtime warning in 26 (DEP0205)
Passing a CryptoKey to node:crypto APIsA KeyObject, or keep the key in Web CryptoRuntime warning in 26 (DEP0203)

Two of these have official codemods:

npx codemod@latest @nodejs/fs-access-mode-constants
npx codemod@latest @nodejs/slow-buffer-to-buffer-alloc-unsafe-slow

The module.register() warning matters if you use custom loaders or a tool that installs them for you (instrumentation and test tooling are the usual places). It still works, but it will be removed in a later version, so check that your tools have moved to registerHooks().

Corepack is no longer bundled

Since Node 25, Corepack is not shipped with Node. If your projects use pnpm or Yarn through the packageManager field and corepack enable, CI and Docker builds on 26 will fail at that step until you install it yourself:

FROM node:26-bookworm-slim
RUN npm install -g corepack && corepack enable

Native addons

NODE_MODULE_VERSION is 147 on Node 26 and 137 on Node 24, so any addon compiled against the Node ABI has to be rebuilt or needs a prebuilt binary for 26. Addons built on Node-API are ABI stable and are meant to run on later majors without recompiling (their own external libraries may still need attention). In practice: delete node_modules, reinstall on 26, and do not reuse a Docker layer cache from a Node 24 image.

The new release schedule

Node.js 26 is the last major to follow the odd/even model. From Node 27, the project moves to one major release a year:

  • Alpha for six months (October to March), for library authors and CI, with semver-major changes allowed and versions like 27.0.0-alpha.1.
  • Current for six months (April to October).
  • LTS for 30 months, so 36 months of support from the first Current release.
  • Every release becomes LTS. There are no more short-lived odd versions to skip.
  • Version numbers follow the calendar year of the first Current release: 27.0.0 in 2027, 28.0.0 in 2028.

For Node 27, the first Alpha build (27.0.0-alpha.0) was published on 29 October 2026, the day after 26 became LTS; 27.0.0 is planned for April 2027, LTS for October 2027, and end of life for 30 April 2030.

If you only ever run LTS, very little changes: one upgrade window a year, every October, with a predictable 30-month runway. If you maintain packages, add the Alpha line to your CI matrix early, which is exactly what the project asks for. The odd releases used to be where breakage showed up first; now the Alpha is.

Hosting and tooling checks

Check these before you change any production runtime:

  • Docker: the official node:26, node:26-bookworm-slim, node:26-trixie-slim and node:26-alpine tags exist. On 14 October, node:lts still pointed at the same image as node:24. If you build from node:lts, expect it to follow 26 after the promotion without any change on your side, so pin the major instead.
  • AWS Lambda: nodejs26.x is in public preview, which AWS says is not for production workloads. Its target for general availability is November 2026.
  • Vercel: the Node.js versions page lists 24.x (the default) and 22.x. I would wait until 26.x appears there, then set it with engines.

Make the version explicit everywhere it is read:

{
  "engines": { "node": "26.x" }
}
strategy:
  matrix:
    node: [22, 24, 26]

Upgrade checklist

  1. Apply the October 2026 security release on the line you run today (26.12.1 or later, 24.22.2 or later).
  2. Run the test suite on 26 with deprecations as errors: NODE_OPTIONS=--throw-deprecation npm test. That turns every runtime warning above into a failing test with a stack trace.
  3. Search for the removed APIs in the table, including inside node_modules, and update the dependencies that use them.
  4. Rebuild native addons from a clean install.
  5. Install Corepack explicitly if you rely on it.
  6. Check TypeScript execution if you run .ts files directly: no enums, no transform flag.
  7. Check loader hooks and instrumentation for module.register().
  8. Confirm your platform supports 26 (Docker base image, Lambda, Vercel, your CI runners).
  9. Pin the major in engines, .nvmrc and the Dockerfile so local, CI and production agree.
  10. Ship to staging first, then production, with the previous image ready to roll back.

Should you upgrade now?

  • On Node 22: yes, plan it this quarter. You have until April 2027. Going straight to 26 is reasonable if your host supports it; otherwise 24 is a safe stop.
  • On Node 24: no rush. It is supported until April 2028. Node 26 is LTS, so test it now and move when your platforms are ready.
  • New projects: start on 26 now that it is LTS, provided your host offers it.

If a Node service is already open for other work, such as moving an MCP server to MCP's stateless spec, that is a good moment to change the runtime too. If you are still deciding whether Node is the right backend at all, I wrote up how I choose in Laravel vs Node.js.

Need a hand?

Upgrading a production Node.js backend, or building a new product on it? See Idea to launch, or email devusamaworks@gmail.com or WhatsApp +92 303 8004684 for a free 30-minute call.

A question about this article?Ask me on WhatsApp

Keep reading

Open for new work

Have a system that needs to scale?

Bring your architecture problem, automation bottleneck, or product idea. We will work out the right engineering path before you spend more time or money.

Free, 30 minutes, no pitch. You leave with a next step either way.