Node.js 26 moved into long-term support (LTS) on October 28, 2026, with the release of version 26.13.0 under the codename Lithium. The release notes say the line will continue to receive updates through to the end of April 2029.

Version 26.13.0 adds no new features. Apart from updating metadata, such as the process.release object, to show that the release is LTS, it is the same as Node.js 26.12.1. The label still matters: the Node.js project says that production applications should only use Active LTS or Maintenance LTS releases.

What is in Node.js 26

Node.js 26 was first released on May 5, 2026, as a Current release. Its main changes include:

  • The Temporal API, a modern date and time API for JavaScript, is enabled by default as an alternative to the older Date object.
  • The V8 JavaScript engine is updated to version 14.6, which adds methods such as Map.prototype.getOrInsert() and Iterator.concat().
  • Undici, the HTTP client built into Node.js, is updated to version 8.
  • Some old features are removed, including http.Server.prototype.writeHeader() (use writeHead() instead) and the legacy _stream_* modules, such as _stream_readable.

Anyone moving from an earlier LTS line, such as Node.js 24 or 22, should note one Linux detail from the release notes. Since Node.js 25, the official Linux binaries are linked against libatomic, which may need to be installed separately depending on the Linux distribution.

Which version should you use?

The Node.js Release Working Group schedule now lists three supported LTS lines. Node.js 26 (Lithium) is in Active LTS until October 20, 2027, and reaches end of life on April 30, 2029. Node.js 24 (Krypton) moved to Maintenance LTS on October 20, 2026, and ends on April 30, 2028. Node.js 22 (Jod) is also in maintenance and ends on April 30, 2027. The project’s releases page lists Node.js 20 as end of life.

A quick way to see which line a computer is running is to print the version and the LTS codename together. The Node.js documentation says process.release.lts holds the LTS codename and is undefined for other release types, including Current releases.

node -p "process.version + ' ' + process.release.lts"

On a machine running Node.js 24.19.0, this prints:

v24.19.0 Krypton

On Node.js 26.13.0 or later, the second word will be Lithium. On a Current release, it will be undefined.

A new release model starts with Node.js 27

Node.js 26 is the last line under the old pattern. Until now, even-numbered versions moved to LTS, while odd-numbered versions stopped getting support after six months. Starting with Node.js 27, the project says, the release cycle will be annual, and every major version will move to LTS after a six-month Current phase, which itself follows six months as an Alpha.

The first alpha of Node.js 27 appeared on October 29, 2026, as version 27.0.0-alpha.0.0.0. The Release Working Group says alpha releases are intended for library authors and continuous integration pipelines, not for production use, and that their API may change between releases. Under the current schedule, Node.js 27 becomes Current on April 22, 2027, and moves to LTS on October 20, 2027. The working group notes that dates are subject to change.

Why it matters

The LTS label is the project’s own signal that a line is ready for real use. For students and self-taught developers, that makes Node.js 26 a sensible choice for a new project or a portfolio app that will run on a server, with updates promised until the end of April 2029. Projects still on Node.js 22 have until April 30, 2027, to move.

Node.js 26 also makes Temporal available by default, so learners can try the modern date and time API without extra flags. Because some legacy features have been removed, it is worth running a project’s tests on Node.js 26 before switching, especially for older code that uses the removed stream modules or writeHeader().

What to watch

Further Node.js 27 alpha releases will show which breaking changes are coming next year. Under the new model, Node.js 27 will also be the first odd-numbered line to become LTS.