mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-24 12:10:08 +01:00
Code Issues Releases Activity
Cross-platform JavaScript runtime environment https://nodejs.org/
42,640 Commits 52 Branches 857 Tags 1.9 GiB
JavaScript 61.7%
C++ 22.7%
Python 10.9%
C 3%
HTML 0.7%
Other 0.9%
80b56bbab0
Go to file
simon-id 80b56bbab0
diagnostics_channel: fix unsubscribe during publish 
PR-URL: https://github.com/nodejs/node/pull/55116
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Reviewed-By: Claudio Wunder <cwunder@gnome.org>
2024-10-14 10:55:39 +00:00
.configurations build,win: add winget config to set up env 2024-09-30 15:17:20 +00:00
.devcontainer
.github meta: bump codecov/codecov-action from 4.5.0 to 4.6.0 2024-10-11 19:19:28 +00:00
android-patches
benchmark events: optimize EventTarget.addEventListener 2024-10-14 10:24:32 +00:00
deps deps: update libuv to 1.49.1 2024-10-14 06:51:18 +00:00
doc Revert "deps: disable io_uring support in libuv by default" 2024-10-14 06:51:19 +00:00
lib diagnostics_channel: fix unsubscribe during publish 2024-10-14 10:55:39 +00:00
src src: remove uv__node_patch_is_using_io_uring 2024-10-14 06:51:19 +00:00
test diagnostics_channel: fix unsubscribe during publish 2024-10-14 10:55:39 +00:00
tools build,win: enable pch for clang-cl 2024-10-11 10:28:55 +00:00
typings lib: remove Symbol[Async]Dispose polyfills 2024-10-07 09:47:44 +00:00
.clang-format Revert "build: upgrade clang-format to v18" 2024-09-18 15:58:34 +00:00
.cpplint src: modernize likely/unlikely hints 2024-09-30 18:04:16 +00:00
.editorconfig
.gitattributes
.gitignore build,win: add winget config to set up env 2024-09-30 15:17:20 +00:00
.gitpod.yml
.mailmap meta: add mailmap entry for abmusse 2024-09-30 22:51:34 +00:00
.nycrc build: fix not valid json in coverage 2024-09-30 20:27:55 +00:00
.yamllint.yaml
android_configure.py
android-configure build: support up to python 3.13 in android-configure 2024-09-21 09:20:53 -07:00
BSDmakefile
BUILD.gn
BUILDING.md doc: reflect toolchains used for official binaries 2024-09-20 01:51:34 +00:00
CHANGELOG.md 2024-10-03, Version 20.18.0 'Iron' (LTS) 2024-10-03 19:54:20 +02:00
CODE_OF_CONDUCT.md
codecov.yml build: update gcovr to 7.2 and codecov config 2024-07-27 21:52:23 +00:00
common.gypi deps: V8: backport 0d5d6e71bbb0 2024-10-03 17:22:10 +02:00
configure build: update required python version to 3.8 2024-08-23 21:20:32 +00:00
configure.py build: add the option to generate compile_commands.json in vcbuild.bat 2024-09-21 09:00:01 -07:00
CONTRIBUTING.md
eslint.config.mjs lib: prefer logical assignment 2024-10-09 06:42:16 +00:00
glossary.md doc, meta: add PTAL to glossary 2024-07-14 17:53:46 +00:00
GOVERNANCE.md
LICENSE doc: run license-builder 2024-09-09 14:33:37 +00:00
Makefile build: fix make errors that occur in Makefile 2024-10-14 06:41:11 +00:00
node.gni deps: allow amaro to be externalizable 2024-09-05 14:27:30 -04:00
node.gyp deps: allow amaro to be externalizable 2024-09-05 14:27:30 -04:00
node.gypi build,win: enable pch for clang-cl 2024-10-11 10:28:55 +00:00
onboarding.md doc: edit onboarding guide to clarify when mailmap addition is needed 2024-10-11 13:30:32 +00:00
pyproject.toml meta: remove unneeded ignore rules from ruff 2024-09-18 17:07:37 +02:00
README.md doc: add release key for aduh95 2024-10-10 12:12:53 +00:00
SECURITY.md meta: fix links in SECURITY.md 2024-09-03 16:38:27 +00:00
suppressions.supp
tsconfig.json
unofficial.gni build: disable ICF for mksnapshot 2024-08-16 16:04:25 +02:00
vcbuild.bat build: add the option to generate compile_commands.json in vcbuild.bat 2024-09-21 09:00:01 -07:00

README.md

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

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

Release types

  • Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v22.x). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life of 8 months. Releases appearing each April convert to LTS (see below) each October.
  • LTS: Releases that receive Long Term Support, with a focus on stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 12 months of Active LTS support and a further 18 months of Maintenance. LTS release lines have alphabetically-ordered code names, beginning with v4 Argon. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Code from the Current branch built every 24-hours when there are changes. Use with caution.

Current and LTS releases follow semantic versioning. A member of the Release Team signs each Current and LTS release. For more information, see the Release README.

Download

Binaries, installers, and source tarballs are available at https://nodejs.org/en/download/.

Current and LTS releases

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.

Nightly releases

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.

API documentation

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/.

Verifying binaries

Download directories contain a SHASUMS256.txt file with SHA checksums for the files.

To download SHASUMS256.txt using curl:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt

To check that a downloaded file matches the checksum, run it through sha256sum with a command such as:

grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -

For Current and LTS, the GPG detached signature of SHASUMS256.txt is in SHASUMS256.txt.sig. You can use it with gpg to verify the integrity of SHASUMS256.txt. You will first need to import the GPG keys of individuals authorized to create releases.

See Release keys for commands to import active release keys.

Next, download the SHASUMS256.txt.sig for the release:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig

Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify the file's signature.

Building Node.js

See BUILDING.md for instructions on how to build Node.js from source and a list of supported platforms.

Security

For information on reporting security vulnerabilities in Node.js, see SECURITY.md.

Contributing to Node.js

Current project team members

For information about the governance of the Node.js project, see GOVERNANCE.md.

TSC (Technical Steering Committee)

TSC voting members

TSC regular members

TSC emeriti members

TSC emeriti members

Collaborators

Emeriti

Collaborator emeriti

Collaborators follow the Collaborator Guide in maintaining the Node.js project.

Triagers

Triagers follow the Triage Guide when responding to new issues.

Release keys

Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):

To import the full set of trusted release keys (including subkeys possibly used to sign releases):

gpg --keyserver hkps://keys.openpgp.org --recv-keys C0D6248439F1D5604AAFFB4021D900FFDB233756 # Antoine du Hamel
gpg --keyserver hkps://keys.openpgp.org --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C # Beth Griggs
gpg --keyserver hkps://keys.openpgp.org --recv-keys 141F07595B7B3FFE74309A937405533BE57C7D57 # Bryan English
gpg --keyserver hkps://keys.openpgp.org --recv-keys 74F12602B6F1C4E913FAA37AD3A89613643B6201 # Danielle Adams
gpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7 # Juan José Arboleda
gpg --keyserver hkps://keys.openpgp.org --recv-keys CC68F5A3106FF448322E48ED27F5E38D5B0A215F # Marco Ippolito
gpg --keyserver hkps://keys.openpgp.org --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600 # Michaël Zasso
gpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4 # Rafael Gonzaga
gpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C # Richard Lau
gpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A # Ruy Adorno
gpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0 # Ulises Gascón

See Verifying binaries for how to use these keys to verify a downloaded file.

Other keys used to sign some previous releases

Security release stewards

When possible, the commitment to take slots in the security release steward rotation is made by companies in order to ensure individuals who act as security stewards have the support and recognition from their employer to be able to prioritize security releases. Security release stewards manage security releases on a rotation basis as outlined in the security release process.

License

Node.js is available under the MIT license. Node.js also includes external libraries that are available under a variety of licenses. See LICENSE for the full license text.