Node.js Reference ยท Concepts and Pitfalls
Node.js release lines and LTS
How Node.js versions work: Current, Active LTS and Maintenance phases, even and odd major releases, codenames, semantic versioning and an upgrade policy.
Node.js ships a new major version on a regular schedule. Each major release moves through phases: first Current (new features, still settling), then, for even-numbered majors, Active LTS (long-term support, recommended for production), then Maintenance (only critical fixes and security patches), and finally End-of-Life (no updates at all). Odd-numbered majors skip the LTS phases and are short-lived.
Production applications should run an LTS line. This site's examples run on Node 24, an LTS line with the codename Krypton. The exact dates of each phase are published on the official Node.js release page, which is the authority; they have been about six months for Current and roughly two and a half years of combined LTS support, so plan upgrades by checking that page rather than relying on memory.
console.log(process.version); // 'v24.22.0' console.log(process.release.lts); // 'Krypton' on an LTS line
Try it
Press Run (or Ctrl + Enter) to see the result here.
Program input ยท what you'd type while the program runs
Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.
Press Run (or Ctrl + Enter) to see the result here.
Program input ยท what you'd type while the program runs
Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.
The phases
| Phase | What it means | Use it for |
|---|---|---|
| Current | New features land; the major version is settling. | Trying new things in development and testing libraries. |
| Active LTS | Stable, with bug fixes and security patches. | Production. |
| Maintenance | Critical bug and security fixes only. | Production while you plan the move to the next LTS. |
| End-of-Life | No more releases. | Nothing; upgrade. |
A release line becomes LTS when it is promoted in the autumn after its April release (even-numbered majors only). The codename of an LTS line is a chemical element name in alphabetical order across the years (Hydrogen, Iron, Jod, Krypton for 18, 20, 22, 24).
Semantic versioning
Node follows semver for its public API: a major may break things, a minor adds features, a patch fixes bugs. In practice some changes need care even in a minor:
- Security releases can tighten behavior to close a hole.
- Features marked experimental may change in any release; see Stability index.
- Deprecations announce removals one or more majors ahead.
Usage notes
- Pin the version for the team. Put the supported range in
package.jsonas"engines": { "node": ">=24" }, and add a.nvmrcor.node-versionfile for version managers. - Test on the version you deploy. CI should use the same major as production, and also the next LTS before you upgrade.
- Upgrade one LTS at a time (22 to 24, not 20 to 24). Read the release notes for breaking changes and check each deprecation warning in your logs.
- Treat deprecation warnings as a to-do list. Run with
--throw-deprecationin tests to fail fast. - Docker images should use a specific tag such as
node:24-slim, notlatest. - Native addons and some packages are built for a Node ABI (
process.versions.modules) and must be rebuilt on a new major. - Check support, not just features. A newer odd release may have a feature you want, but it will lose security fixes within months.