Skip to content
Node.js JavaScript runtime 🐢🚀
JavaScript C++ Python C HTML Makefile Other
Branch: master
Clone or download

Latest commit

addaleax worker: emit `'messagerror'` events for failed deserialization
This is much nicer than just treating exceptions as uncaught, and
enables reporting of exceptions from the internal C++ deserialization
machinery.

PR-URL: #33772
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Latest commit e1ad548 Jun 8, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github build: output dots in "Build from tarball" action Jun 6, 2020
benchmark tools: update ESLint to 7.2.0 Jun 13, 2020
deps deps: V8: cherry-pick 4e1bf2bc92bd Jun 8, 2020
doc worker: emit `'messagerror'` events for failed deserialization Jun 14, 2020
lib worker: emit `'messagerror'` events for failed deserialization Jun 14, 2020
src worker: emit `'messagerror'` events for failed deserialization Jun 14, 2020
test worker: emit `'messagerror'` events for failed deserialization Jun 14, 2020
tools tools: update ESLint to 7.2.0 Jun 13, 2020
.clang-format tools: add `make format-cpp` to run clang-format on C++ diffs Aug 3, 2018
.cpplint tools: move cpplint configuration to .cpplint Apr 8, 2019
.editorconfig tools: change editorconfig's 'ignore' to 'unset' Jun 30, 2019
.eslintignore test: run eslint on test file and fix errors Dec 15, 2018
.eslintrc.js lib: initial experimental AbortController implementation Jun 5, 2020
.flake8 tools: python: ignore instead of select flake8 rules Apr 14, 2019
.gitattributes build,win: fix Python detection on localized OS Sep 6, 2019
.gitignore build: remove `.txt` files from .gitignore Apr 10, 2020
.mailmap doc: update AUTHORS list Mar 30, 2020
.nycrc test: fix tests that fail under coverage May 22, 2018
AUTHORS doc: update AUTHORS list Mar 30, 2020
BSDmakefile node: rename from io.js to node Aug 23, 2015
BUILDING.md build: drop support for VS2017 Jun 12, 2020
CHANGELOG.md 2020-06-02, Version 10.21.0 'Dubnium' (LTS) Jun 2, 2020
CODE_OF_CONDUCT.md doc: simplify CODE_OF_CONDUCT.md Nov 2, 2018
CONTRIBUTING.md doc: improve doc/markdown file organization coherence Mar 4, 2020
GOVERNANCE.md doc: fix more links Apr 2, 2020
LICENSE doc,tools: properly syntax highlight API ref docs May 23, 2020
Makefile build: add LINT_CPP_FILES to checkimports check Jun 8, 2020
README.md doc: add lint disabling comment for collaborator list Jun 4, 2020
SECURITY.md doc: synch SECURITY.md with website Apr 19, 2020
android-configure build: support android build on ndk version equal or above 23 Mar 11, 2020
common.gypi deps: V8: cherry-pick 4e1bf2bc92bd Jun 8, 2020
configure build: fix inability to detect correct python command in configure May 25, 2020
configure.py src,build: add --openssl-default-cipher-list Jun 8, 2020
glossary.md doc: add angle brackets around implicit links Apr 24, 2020
node.gyp worker: allow passing JS wrapper objects via postMessage Jun 14, 2020
node.gypi tools: update V8 gypfiles for 8.1 Mar 18, 2020
onboarding.md doc: add angle brackets around implicit links Apr 24, 2020
vcbuild.bat build: drop support for VS2017 Jun 12, 2020

README.md

Node.js

Node.js is an open-source, cross-platform, JavaScript runtime environment. It executes JavaScript code outside of a browser. For more 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.

This project is bound by 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, v10.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 codenames, 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-carbon directory contains the latest Carbon (Node.js 8) 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 SHASUM256.txt. You will first need to import the GPG keys of individuals authorized to create releases. To import the keys:

$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

See the bottom of this README for a full 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 Emeriti

Collaborators

Collaborator Emeriti

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

Release Keys

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

To import the full set of trusted release keys:

gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver pool.sks-keyservers.net --recv-keys A48C2BEE680E841632CD4E44F07496B3EB3C1762
gpg --keyserver pool.sks-keyservers.net --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C

See the section above on Verifying Binaries for how to use these keys to verify a downloaded file.

Other keys used to sign some previous releases:

You can’t perform that action at this time.