Node.js Releases

Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.

Release Schedule

Releases

Full details regarding the Node.js release schedule are available on GitHub.

Commercial Support

Commercial support for versions past the Maintenance phase is available through our OpenJS Ecosystem Sustainability Program partner HeroDevs.

Looking for the latest release of a version branch?

Node.jsN-APICodenameReleased atnpm
v23.5.0v131-v10.9.2ReleasesChangelogDocs
v22.12.0v127Jodv10.9.0ReleasesChangelogDocs
v21.7.3v120-v10.5.0ReleasesChangelogDocs
v20.18.1v115Ironv10.8.2ReleasesChangelogDocs
v19.9.0v111-v9.6.3ReleasesChangelogDocs
v18.20.5v108Hydrogenv10.8.2ReleasesChangelogDocs
v17.9.1v102-v8.11.0ReleasesChangelogDocs
v16.20.2v93Galliumv8.19.4ReleasesChangelogDocs
v15.14.0v88-v7.7.6ReleasesChangelogDocs
v14.21.3v83Fermiumv6.14.18ReleasesChangelogDocs
v13.14.0v79-v6.14.4ReleasesChangelogDocs
v12.22.12v72Erbiumv6.14.16ReleasesChangelogDocs
v11.15.0v67-v6.7.0ReleasesChangelogDocs
v10.24.1v64Dubniumv6.14.12ReleasesChangelogDocs
v9.11.2v59-v5.6.0ReleasesChangelogDocs
v8.17.0v57Carbonv6.13.4ReleasesChangelogDocs
v7.10.1v51-v4.2.0ReleasesChangelogDocs
v6.17.1v48Boronv3.10.10ReleasesChangelogDocs
v5.12.0v47-v3.8.6ReleasesChangelogDocs
v4.9.1v46Argonv2.15.11ReleasesChangelogDocs
v0.12.18v14-v2.15.11ReleasesChangelogDocs

Official versus Community

The Node.js website offers numerous installation methods that allow Node.js to be installed in a non-interactive manner, for example, via CLIs, OS package managers (such as apt), or Node.js version managers (such as nvm).

The Node.js project, in an attempt to popularize and advertise community efforts, has introduced a new Downloads page that lists both Official and Community installation methods, providing more versatility and options for users. With this change, we introduced the concept of "Official" and "Community" installation methods. In order to be considered "Official", the installation method must meet the following requirements:

Requirements
New Node.js releases must be available simultaneously upon the official release
Project maintainers have a close relationship with Node.js, including direct communication
Installation method downloads the official binaries bundled by the Node.js project
Installation method does not build from source when binaries are available, or alter the official binaries provided by Node.js
Reading Time
2 min read
Contribute
Edit this page
Table of Contents
  1. Release Schedule
  2. Commercial Support
  3. Looking for the latest release of a version branch?
  4. Official versus Community