Back to results for “Deployment”
Node.js › Node.js Fundamentals & Runtime Architecture

What is the Node.js LTS (Long-Term Support) release schedule, and why does it matter for choosing which version to run in production?

Intermediate

Answer

Node.js follows a predictable release cadence where a new major version is released roughly every six months, alternating between 'Current' (receiving the latest features, but with shorter overall support) and eventually being promoted to 'LTS' status (receiving critical bug fixes and security patches for a much longer period, typically 30 months total) -- production applications should generally run an Active or Maintenance LTS release rather than a Current release, prioritizing the stability and long support window LTS versions provide over access to the very latest, less-battle-tested features.
# Checking and managing Node.js versions, commonly with a version manager like nvm
nvm ls-remote --lts   # lists available LTS versions
nvm install --lts     # installs the latest LTS release
nvm use 20            # switches to a specific major version
Real-world example A company's production deployment pins to the current Active LTS version of Node.js (rather than the newest Current release) specifically to benefit from its long, predictable support window and the greater confidence that comes from a version that's already been running in production across the broader Node.js ecosystem for months.

Common follow-ups: What's the practical difference between the 'Current', 'Active LTS', and 'Maintenance LTS' phases in terms of what kind of updates each still receives?;How do you plan and execute an upgrade from one major LTS version to the next with minimal production risk?