README

Node.js

Node.js is an open-source, cross-platform JavaScript runtime environment.

For information on using Node.js, see the [Node.js website][].

The Node.js project uses an open governance model. The
[OpenJS Foundation][] provides support for the project.

Contributors are expected to act in a collaborative manner to move
the project forward. We encourage the constructive exchange of contrary
opinions and compromise. The TSC
reserves the right to limit or block contributors who repeatedly act in ways
that discourage, exhaust, or otherwise negatively affect other participants.

This project has a [Code of Conduct][].

 Table of contents

 Support
 Release types
   Download
     Current and LTS releases
     Nightly releases
     API documentation
   Verifying binaries
 Building Node.js
 Security
 Contributing to Node.js
 Current project team members
   TSC (Technical Steering Committee)
   Collaborators
   Triagers
   Release keys
 License

 Support

Looking for help? Check out the
instructions for getting support.

 Release types

Node.js follows semantic versioning.

 Alpha: Under active development where semver-major changes are allowed.
  Each October, a new release line (for example, Node.js 27) branches off main
  and receives Alpha releases (for example, 27.0.0-alpha.0.0.0) for 6 months,
  then are promoted to Current (see below) each April. Alpha releases are signed,
  tagged, and tested through CITGM, but their
  API and ABI may change between releases. They are intended for library authors
  and CI pipelines, not for production use.
 Current: Under active development, no semver-major changes allowed. Node.js
  releases a new major version once a year, in April. Releases stay Current for
  6 months, then convert to LTS (see below) each October. Their ABI may change
  between releases. They are intended for library authors and CI pipelines, not
  for production use.
 LTS: Releases under Long Term Support, with a focus on stability
  and security. Only changes that have been on Alpha or Current release for two
  weeks can be backported to a typical LTS release. Every major version becomes an LTS
  release, and receives 30 months of LTS support, for a total of 36 months from
  its first Current release to End-of-Life. LTS release lines have alphabetically-ordered
  code names, beginning with Node.js 4 Argon.
 Nightly: Code from the main branch built every 24-hours when there are
  changes. Unlike Alpha releases, nightly builds are automated and untested.
  Use with caution.

Release lines up to and including Node.js 26 follow the previous schedule, where a
new major version was released every 6 months and only even-numbered major
versions became LTS. See the
Node.js release schedule announcement
for details.

For more information, see the
Release README.

 Download

Binaries, installers, and source tarballs are available at
.

 Current and LTS releases



The latest directory is an
alias for the latest Current release. The latest-_codenam

Top issues

Latest release

Notable Changes

This release marks the transition of Node.js 26.x into Long Term Support (LTS)
with the codename 'Lithium'. It will continue to receive updates through to
the end of April 2029.

Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 26.12.1 are included.

If you are updating from an earlier Long Term Support release (e.g. Node.js 24
or 22 or earlier) please note that since Node.js 25 the official binaries for
Linux are linked against libatomic, which may need to be installed separately