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][].
Looking for help? Check out the instructions for getting support.
Node.js follows semantic versioning.
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.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.
Binaries, installers, and source tarballs are available at https://nodejs.org/en/download/.
https://nodejs.org/download/release/
The latest directory is an alias for the latest Current release. The latest-codename directory is an alias for the latest release from an LTS line. For example, the latest-hydrogen directory contains the latest Hydrogen (Node.js 18) release.
https://nodejs.org/download/nightly/
Each directory and filename includes the version (e.g., v22.0.0),
followed by the UTC date (e.g., 20240424 for April 24, 2024),
and the short commit SHA of the HEAD of the release (e.g., ddd0a9e494).
For instance, a full directory name might look like v22.0.0-nightly20240424ddd0a9e494.
Documentation for the latest Current release is at https://nodejs.org/api/. Version-specific documentation is available in each release directory in the docs subdirectory. Version-specific documentation is also at https://nodejs.org/download/docs/.
Download directories contain a SHASUMS256.txt.asc file with SHA checksums for the
files and the releaser PGP signature.
You can get a trusted keyring from nodejs/release-keys, e.g. using curl:
curl -fsLo "/path/to/nodejs-keyring.kbx" "https://github.com/nodejs/release-keys/raw/HEAD/gpg/pubring.kbx"
Alternatively, you can import the releaser keys in your default keyring, see Release keys for commands on how to do that.
Then, you can verify the files you've downloaded locally
(if you're using your default keyring, pass --keyring="${GNUPGHOME:-~/.gnupg}/pubring.kbx"):
curl -fsO "https://nodejs.org/dist/${VERSION}/SHASUMS256.txt.asc" \
&& gpgv --keyring="/path/to/nodejs-keyring.kbx" --output SHASUMS256.txt < SHASUMS256.txt.asc \
&& shasum --check SHASUMS256.txt --ignore-missing
See BUILDING.md for instructions on how to build Node.js from source and a list of supported platforms.
For information on reporting security vulnerabilities in Node.js, see SECURITY.md.
For information about the governance of the Node.js project, see GOVERNANCE.md.
| 日期 | 榜单 | 排名 | 周期新增 | 总 STAR |
|---|