Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
Node.js JavaScript runtime ✨🐢🚀✨
40,741 Commits 48 Branches 857 Tags 1.8 GiB
JavaScript 61.7%
C++ 22.7%
Python 10.9%
C 3%
HTML 0.7%
Other 0.9%
0161ad0baf
Go to file
mary marchini 0161ad0baf
inspector: add NodeRuntime.waitingForDebugger event 
`NodeRuntime.waitingForDebugger` is a new Inspector Protocol event that
will fire when the process being inspected is waiting for the debugger
(for example, when `inspector.waitForDebugger()` is called). This allows
inspecting processes to know when the inspected process is waiting for a
`Runtime.runIfWaitingForDebugger` message to resume execution. It allows
tooling to resume execution of the inspected process as soon as it deems
necessary, without having to guess if the inspected process is waiting
or not, making the workflow more deterministic. With a more
deterministic workflow, it is possible to update Node.js core tests to
avoid race conditions that can cause flakiness. Therefore, tests were
also changed as following:

  * Remove no-op Runtime.runIfWaitingForDebugger from tests that don't
    need it
  * Use NodeRuntime.waitingForDebugger in all tests that need
    Runtime.runIfWaitingForDebugger, to ensure order of operations is
    predictable and correct
  * Simplify test-inspector-multisession-ws

There might be value in adding `NodeWorker.waitingForDebugger` in a
future patch, but as of right now, no Node.js core inspector tests using
worker threads are not failing due to race conditions.

Fixes: https://github.com/nodejs/node/issues/34730
PR-URL: https://github.com/nodejs/node/pull/51560
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
2024-02-23 22:46:29 +00:00
.devcontainer build: fix for VScode "Reopen in Container" 2023-12-31 01:26:30 +00:00
.github benchmark: rename startup.js to startup-core.js 2024-02-21 00:15:46 +01:00
android-patches build: rewritten the Android build system 2022-09-12 08:10:29 +00:00
benchmark benchmark: rename startup.js to startup-core.js 2024-02-21 00:15:46 +01:00
deps build: do not rely on gn_helpers in GN build 2024-02-23 20:49:43 +09:00
doc build,tools: make addons tests work with GN 2024-02-23 16:14:42 +09:00
lib src: simplify embedder entry point execution 2024-02-23 01:50:27 +00:00
src inspector: add NodeRuntime.waitingForDebugger event 2024-02-23 22:46:29 +00:00
test inspector: add NodeRuntime.waitingForDebugger event 2024-02-23 22:46:29 +00:00
tools build: do not rely on gn_helpers in GN build 2024-02-23 20:49:43 +09:00
typings async_hooks,inspector: implement inspector api without async_wrap 2024-01-24 13:29:28 +00:00
.clang-format tools: add make format-cpp to run clang-format on C++ diffs 2018-08-03 19:40:23 +08:00
.cpplint tools: move cpplint configuration to .cpplint 2019-04-08 08:30:29 -04:00
.editorconfig tools: enforce use of single quotes in editorconfig 2020-11-12 06:19:49 +00:00
.eslintignore esm: use import attributes instead of import assertions 2023-10-14 03:52:38 +00:00
.eslintrc.js esm: use import attributes instead of import assertions 2023-10-14 03:52:38 +00:00
.gitattributes build: add .gitattributes for npm and other shims 2022-07-19 21:27:49 +01:00
.gitignore meta: add .temp and .lock tags to ignore 2024-01-04 19:01:42 +00:00
.gitpod.yml doc,tools: switch to @node-core/utils 2023-09-25 11:48:03 +00:00
.mailmap meta: add .mailmap entry for lemire 2024-01-29 22:09:16 +00:00
.nycrc test: add windows and C++ coverage 2020-10-21 19:41:08 -07:00
.yamllint.yaml build: extend yamllint configuration 2022-02-14 19:09:26 +01:00
android_configure.py zlib: fix discovery of cpu-features.h for android 2023-09-29 11:52:46 -04:00
android-configure build: add python 3.11 support for android 2022-12-11 02:58:02 +00:00
BSDmakefile build: replace which with command -v 2020-11-19 19:33:28 +01:00
BUILD.gn build: add GN build files 2023-11-11 09:51:05 +00:00
BUILDING.md doc: bump FreeBSD experimental support to 13.2 2023-12-22 09:26:09 +00:00
CHANGELOG.md 2024-02-14, Version 21.6.2 (Current) 2024-02-14 14:12:25 -03:00
CODE_OF_CONDUCT.md tools: avoid unnecessary escaping in markdown formatter 2021-10-31 09:36:05 -07:00
codecov.yml tools: disable Codecov commit statuses 2023-04-01 07:08:22 +00:00
common.gypi deps: V8: cherry-pick efb1133eb894 2024-02-01 11:53:59 +00:00
configure build: support Python 3.12 2023-11-06 14:11:01 +00:00
configure.py build: build opt to set local location of headers 2024-02-15 16:41:37 -05:00
CONTRIBUTING.md doc: make contributing info more discoverable 2022-01-18 14:24:30 -05:00
glossary.md doc: add undici to glossary 2022-06-08 17:22:09 -07:00
GOVERNANCE.md meta: clarify nomination process according to Node.js charter 2023-11-26 17:14:19 +00:00
LICENSE doc: the GN files should use Node's license 2023-12-28 20:27:05 +00:00
Makefile build,tools: make addons tests work with GN 2024-02-23 16:14:42 +09:00
node.gni build: remove copyright header in node.gni 2024-01-24 02:11:08 +00:00
node.gyp build: encode non-ASCII Latin1 characters as one byte in JS2C 2024-02-17 17:09:24 +00:00
node.gypi src: fix dynamically linked zlib version 2023-12-04 17:30:58 +00:00
onboarding.md doc,tools: switch to @node-core/utils 2023-09-25 11:48:03 +00:00
pyproject.toml tools: skip ruff on tools/gyp 2023-10-31 12:44:37 +00:00
README.md doc: add Paolo to TSC members 2024-02-21 22:26:59 +00:00
SECURITY.md doc: mention node:wasi in the Threat Model 2023-12-21 12:55:52 +00:00
tsconfig.json lib: fix internalBinding typings 2023-09-23 10:48:34 +00:00
unofficial.gni build,tools: make addons tests work with GN 2024-02-23 16:14:42 +09:00
vcbuild.bat build,tools: make addons tests work with GN 2024-02-23 16:14:42 +09: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, v19.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 name and filename contains a date (in UTC) and the commit SHA at the HEAD of the release.

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. To import the keys:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C

See Release keys for a script 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 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver hkps://keys.openpgp.org --recv-keys 141F07595B7B3FFE74309A937405533BE57C7D57
gpg --keyserver hkps://keys.openpgp.org --recv-keys 74F12602B6F1C4E913FAA37AD3A89613643B6201
gpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7
gpg --keyserver hkps://keys.openpgp.org --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver hkps://keys.openpgp.org --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4
gpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C
gpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A
gpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0

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.