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.11.0v131-v10.9.2ReleasesChangelogDocs
v22.14.0v127Jodv10.9.2ReleasesChangelogDocs
v21.7.3v120-v10.5.0ReleasesChangelogDocs
v20.19.0v115Ironv10.8.2ReleasesChangelogDocs
v19.9.0v111-v9.6.3ReleasesChangelogDocs
v18.20.8v108Hydrogenv10.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 vs. Community Installation Methods

The Node.js website provides several non-interactive installation methods, including command-line interfaces (CLIs), operating system (OS) package managers (e.g., brew), and Node.js version managers (e.g., nvm).

To highlight and promote community contributions, the Node.js project introduced a revised Downloads page categorizing installation methods as either “Official” or “Community.” This provides users with increased flexibility and choice. To ensure clarity, we’ve defined criteria for each category.

Official Installation Methods

Installation methods designated as “Official” must meet the following requirements:

Requirements (Official Installation Methods)
New Node.js releases must be available simultaneously with the official release.
Project maintainers must have a close relationship with the Node.js project, including direct communication channels.
Installation method must download official binaries bundled by the Node.js project.
Installation method must not build from source when pre-built binaries are available, nor should it alter the official binaries.

Community Installation Methods

Community installation methods included on the self-service download page (/download) must also adhere to a minimum set of criteria:

  • Version Support: Must support all currently supported, non-End-of-Life (EOL) Node.js versions.
  • OS Compatibility: Must function on at least one officially supported Operating System (OS).
  • Broad OS Support: Cannot be limited to a subset of OS distributions or versions.
    • For example, an installation method claiming compatibility with “Windows” must function on “Windows 10”, “Windows 11”, and all their editions (including server versions).
    • Similarly, an installation method claiming compatibility with “Linux” must be installable on all major Linux distributions, not just a specific subset. It cannot rely on distribution-specific package managers like apt or dnf.
Reading Time
2 min
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 vs. Community Installation Methods
  5. Official Installation Methods
  6. Community Installation Methods