Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Upgrades and deprecations

Upgrade Node 18 to the Latest LTS: Hop Order and Dates

In short

The official schedule gives Node.js 18 an end of life of 30 April 2025. The lines in LTS today are 22, 24 and 26, and 26 is the newest. The route is 20, 22, 24, then 26, reading each major's changelog on the way. I would aim for 24 or 26, because 22 itself ends on 30 April 2027.

When did Node 18 reach end of life?

The Node.js release schedule file lists Node 18 (Hydrogen) with LTS from 25 October 2022, maintenance from 18 October 2023 and end of life on 30 April 2025. The releases page shows its last update as 27 March 2025, so its last update is more than 18 months old.

nodejs.org's end-of-life page states that an EOL line receives no further updates, including security patches. It adds that this holds even when a vulnerability found in a newer line also affects the old one.

Checked against: source 1, source 2, source 3

Which Node lines are LTS today?

The table joins the dates in the schedule file with the status on the releases page. The page labels v22, v24 and v26 simply LTS and names v26.13.1 as the latest LTS. I derived Active and Maintenance from the schedule dates myself.

Node 27 is in Alpha. The releases page says that from Node 27 the cycle is annual and every major moves to LTS after its Current phase, so the even-and-odd pattern ends after 26.

LineCodenameLTS sinceMaintenance sinceEnd of lifeStatus on 19 Nov 2026
18Hydrogen25 Oct 202218 Oct 202330 Apr 2025End of life
20Iron24 Oct 202322 Oct 202430 Apr 2026End of life
22Jod29 Oct 202421 Oct 202530 Apr 2027Maintenance LTS
24Krypton28 Oct 202520 Oct 202630 Apr 2028Maintenance LTS
26Lithium28 Oct 202620 Oct 202730 Apr 2029Active LTS

Checked against: source 1, source 2

In what order should the hops go?

I found no official Node upgrade guide that walks from one major to another. What nodejs.org publishes is a changelog per major with a Notable Changes section. The odd lines, 19, 21, 23 and 25, were short-lived Current releases and are listed as end of life, and each has its own changelog.

I would plan the route as 18, 20, 22, 24, 26 and read the notes of the odd lines in between, because a change is listed only in the changelog of the release that made it. Node 20 is already past end of life and 22 ends on 30 April 2027, so I would use both as test checkpoints and ship at 24 or 26.

Checked against: source 1, source 2, source 4, source 5, source 6, source 7, source 8, source 9, source 10, source 11

What do the changelogs list as breaking at each hop?

These are entries from the notes of each major release, mostly under Notable Changes and Deprecations and Removals. They are the ones I would search a codebase for first, and the full notes are longer.

  • 18 to 20: Node 19 turns HTTP keep-alive on by default for outgoing connections, with a 5-second waiting window, removes DTrace, SystemTap and ETW support and runtime-deprecates integer coercion in process.exit(). Node 20 requires the version option in new WASI(), validates Web Crypto arguments against their WebIDL definitions, changes how single executable apps are prepared, warns when url.parse() gets an invalid port and runs ESM loader hooks on a separate thread.
  • 20 to 22: Node 21 removes the ESM globalPreload hook. Node 22 drops import assertions, raises the default stream highWaterMark, enables the WebSocket client by default and moves crypto.createCipher() and createDecipher() to end of life.
  • 22 to 24: Node 23 removes 32-bit Windows support. Node 24 runtime-deprecates url.parse() and SlowBuffer, removes tls.createSecurePair, deprecates calling Zlib classes without new and passing args to spawn and execFile, makes AsyncLocalStorage use AsyncContextFrame by default, renames the permission flag to --permission and requires ClangCL to build on Windows.
  • 24 to 26: Node 25 removes SlowBuffer, fs.F_OK, fs.R_OK, fs.W_OK and fs.X_OK, and moves assert.CallTracker and the rmdir recursive option to end of life. Node 26 removes http.Server.prototype.writeHeader(), the legacy _stream_* modules and --experimental-transform-types, runtime-deprecates module.register() and enables the Temporal API by default.

Checked against: source 4, source 5, source 6, source 7, source 8, source 9, source 10, source 11

Should the route end on Node 24 or 26?

Both are inside the window that nodejs.org says production should use, Active or Maintenance LTS. Node 26 has the longer clock. It is in Active LTS until 20 October 2027 and ends on 30 April 2029, while 24 entered maintenance on 20 October 2026 and ends on 30 April 2028.

For a long-lived application I would choose 26 if your dependencies allow it, and 24 if one of them does not yet. This page compares nodejs.org documents fetched on 19 November 2026. It does not cover your npm packages, native addons or container images, and it does not say your code will pass any hop.

If a hosting platform rejects the version you picked, see this fix page for one example.

Checked against: source 1, source 2

What else do people ask?

Is Node 20 still supported?

No. The official schedule gives Node 20 an end of life of 30 April 2026, and the releases page lists it as EOL. It is a stop on the way from 18, not a destination.

Is Node 22 still a safe target?

It is in Maintenance LTS and the schedule ends it on 30 April 2027, about five months from now. I would treat it as a checkpoint and not as the place to stop.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. This page compares nodejs.org documents I fetched on 19 Nov 2026 (the release schedule file, the releases and end-of-life pages and the changelog of each major from 19 to 26). I did not run these upgrades for it. It does not cover your npm packages, native addons or deployment platform. Found a mistake? Tell me.

Keep reading

Next step

Have a project in mind?

Tell me about it. A discovery call within 48 hours.