Skip to content
Runtime

Node.js Releases

Track every Node.js release including LTS and Current lines. Version timelines, EOL dates, security patches, and upgrade guidance for Node.js developers.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

18 LTS
20 LTS
22 LTS
24 LTS
25 Current
2022 2023 2024 2025 2026 2027 2028 2029
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

18 20 Low Difficulty
Est. 1-2 hours

Breaking Changes

  • fetch() API changes — now globally available
  • V8 engine update to 11.3
  • Permission model introduced (experimental)

Migration Notes

Straightforward upgrade for most apps. Test fetch() usage if you relied on node-fetch. The new permission model is opt-in and won't affect existing code.

20 22 Low Difficulty
Est. 1-2 hours

Breaking Changes

  • V8 engine update to 12.4
  • WebSocket client added (experimental)
  • Native test runner now stable
  • glob() and globSync() added to fs module

Migration Notes

Mostly additive changes. Review any V8-specific code or native addons. The stable test runner may replace your current test framework for simple cases.

22 24 Medium Difficulty
Est. 2-4 hours

Breaking Changes

  • V8 engine update to 13.0
  • require(esm) now supported — changes module resolution
  • Permission model now stable — review security policies
  • WebSocket client now stable
  • npm updated to 11.x with new dependency resolution

Migration Notes

The require(esm) change is significant — test module loading thoroughly. npm 11 may resolve dependencies differently. Review the stable permission model if adopting security hardening.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
Node.js 18 Critical High Degrading Dropping Critical Upgrade immediately
Node.js 20 Medium Low Active Full Medium Plan upgrade to 22
Node.js 22 Low Low Active Full Low Current recommended LTS
Node.js 24 None Low Growing Partial Low Latest LTS — adopt when ready

Risk score combines EOL proximity, known CVEs, ecosystem support, and cloud provider compatibility. Higher risk = more urgent action needed. Assessed as of February 2026.

LTS Version Feature Comparison

Side-by-side feature differences across major versions.

Feature 18 LTS 20 LTS 22 LTS 24 LTS
V8 Engine 10.2 11.3 12.4 13.0
Native fetch() Experimental Stable Stable Stable
Native test runner Experimental Stable Stable Stable
Permission model No Experimental Experimental Stable
ESM support Full Full Full Full + require(esm)
Single executable apps No Experimental Stable Stable
Watch mode No Experimental Stable Stable
WebSocket client No No Experimental Stable
npm version 8.x 10.x 10.x 11.x
Performance (vs 18) Baseline +5-10% +10-15% +15-20%

Embed Badges

Add live Node.js status badges to your README, docs, or dashboard.

Health Status

Overall support health

Node.js Health Status
![Node.js Health Status](https://img.releaserun.com/badge/health/nodejs.svg)

EOL Countdown

Next end-of-life date

Node.js EOL Countdown
![Node.js EOL Countdown](https://img.releaserun.com/badge/eol/nodejs.svg)

Latest Version

Current stable release

Node.js Latest Version
![Node.js Latest Version](https://img.releaserun.com/badge/v/nodejs.svg)

CVE Status

Known vulnerabilities

Node.js CVE Status
![Node.js CVE Status](https://img.releaserun.com/badge/cve/nodejs.svg)

Frequently Asked Questions

Common questions about Node.js releases and lifecycle.

What is the Node.js LTS schedule?
Node.js even-numbered releases enter LTS status and are supported for 30 months. Odd-numbered releases are Current and supported for about 6 months.
Which Node.js version should I use?
Use the latest LTS release for production. Current releases are fine for development and testing new features.
How often does Node.js release updates?
New major versions ship every April and October. Patch releases with security fixes ship as needed throughout the year.
What happens when a Node.js version reaches EOL?
It stops receiving security patches, bug fixes, and npm compatibility updates. Running EOL Node.js in production is a security risk.

Related Tools

Browse All Version History