Skip to content
Node.js JavaScript runtime 🐢🚀
JavaScript C++ Python C HTML Makefile Other
Branch: master
Clone or download
BridgeAR util: improve unicode support
The array grouping function relies on the width of the characters.
It was not calculated correct so far, since it used the string
length instead.
This improves the unicode output by calculating the mono-spaced
font width (other fonts might differ).

PR-URL: #31319
Reviewed-By: James M Snell <>
Reviewed-By: Steven R Loomis <>
Reviewed-By: Rich Trott <>
Reviewed-By: Minwoo Jung <>
Latest commit 8fb5fe2 Jan 11, 2020
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github build: do not use setup-node in build workflows Jan 16, 2020
benchmark benchmark: add default type in getstringwidth.js Jan 16, 2020
deps deps: uvwasi: cherry-pick 941bedf Jan 17, 2020
doc report: add support for Workers Jan 21, 2020
lib util: improve unicode support Jan 22, 2020
src report: add support for Workers Jan 21, 2020
test util: improve unicode support Jan 22, 2020
tools stream: support passing generator functions into pipeline() Jan 18, 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,tools,test: remove custom number-isnan rule Jan 8, 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,win: support building MSI with VS2019 Dec 13, 2019
.mailmap doc: update AUTHORS list Oct 31, 2019
.nycrc test: fix tests that fail under coverage May 22, 2018
.travis.yml tools: allow the travis commit message job to fail Dec 31, 2019
AUTHORS doc: update AUTHORS list Nov 26, 2019
BSDmakefile node: rename from io.js to node Aug 23, 2015 doc: fix anchors and subtitle in Dec 25, 2019 2020-01-21, Version 13.7.0 (Current) Jan 21, 2020 doc: simplify Nov 2, 2018 doc: document "Resume Build" limitation Nov 26, 2019 doc: remove the suffix number of the anchor link Sep 22, 2019 doc: remove extra backtick Jan 4, 2020 doc: update Nov 7, 2019
LICENSE wasi: introduce initial WASI support Nov 30, 2019
Makefile build: fix missing x64 arch suffix in binary tar name Dec 14, 2019 doc: update README to make Node.js description clearer Jan 11, 2020 doc: remove usage of "Node" in favor of "Node.js" Dec 4, 2019
android-configure build: don't create directory for NDK toolchain Mar 22, 2017
common.gypi deps: V8: cherry-pick d89f4ef1cd62 Jan 15, 2020
configure build: use Node.js instead of Node in configure Nov 30, 2019 build: avoid using CMP for BZ2File Jan 8, 2020
node.gyp module: loader getSource, getFormat, transform hooks Jan 6, 2020
node.gypi build: switch realpath to pwd Dec 27, 2019
vcbuild.bat build: remove enable_vtune from vcbuild.bat Jan 15, 2020


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


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.


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

Each directory name and filename contains a date (in UTC time) and the commit SHA at the HEAD of the release.

API Documentation

Documentation for the latest Current release is at Version-specific documentation is available in each release directory in the docs subdirectory. Version-specific documentation is also at

Verifying Binaries

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

To download SHASUMS256.txt using curl:

$ curl -O

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

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

Building Node.js

See 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

Contributing to Node.js

Current Project Team Members

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

TSC (Technical Steering Committee)

TSC Emeriti


Collaborator Emeriti

Collaborators follow the in maintaining the Node.js project.

Release Keys

GPG keys used to sign Node.js releases:

To import the full set of trusted release keys:

gpg --keyserver --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C
gpg --keyserver --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
gpg --keyserver --recv-keys 77984A986EBC2AA786BC0F66B01FBB92821C587A
gpg --keyserver --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver --recv-keys A48C2BEE680E841632CD4E44F07496B3EB3C1762

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.