/node

Node.js JavaScript runtime ✨🐢🚀✨
  1. JavaScript 65.4%
  2. C++ 23.5%
  3. C 5.4%
  4. HTML 2.1%
  5. POV-Ray SDL 1.1%
  6. Python 1.0%
  7. Other 1.5%
JavaScript C++ C HTML POV-Ray SDL Python Other

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP
Find file
Switch branches/tags
Nothing to show
Latest commit 46d3ff2 Jul 23, 2017 @shivanth shivanth committed with silverwind Reviewed-By: Anna Henningsen Reviewed-By: Jeremiah Senkpiel ">repl: do not consider `...` as a REPL command 
This fix makes ... in REPL to be considered as a javascript construct
rather than a REPL keyword.

Fixes: #14426
PR-URL: #14467
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Permalink
Failed to load latest commit information.
.github Reviewed-By: Jeremiah Senkpiel Reviewed-By: Luigi Pinca Reviewed-By: Rich Trott ">doc: fix commit guideline url May 5, 2017
benchmark Reviewed-By: Refael Ackermann Reviewed-By: Timothy Gu Reviewed-By: James M Snell ">lib,src: fix consistent spacing inside braces Jul 21, 2017
deps Reviewed-by: Jakob Gruber Reviewed-by: Ulan Degenbaev Commit-Queue: Yang Guo Cr-Commit-Position: refs/heads/master@{#46732} https://github.com/v8/v8/commit/182caaf4a9b94024e47007d426831c024345cb97 Do not track transitions for built-in objects. Objects created during bootstrapping do not need a transition tree except for elements kind transitions. Bug: v8:6596 Change-Id: I237b8b2792f201336e1c9731c815095dd06bc182 Reviewed-on: https://chromium-review.googlesource.com/571750 Reviewed-by: Igor Sheludko Commit-Queue: Yang Guo Cr-Commit-Position: refs/heads/master@{#46693} Fixes: https://github.com/nodejs/node/issues/14171 PR-URL: https://github.com/nodejs/node/pull/14345 Reviewed-By: Refael Ackermann Reviewed-By: Ben Noordhuis Reviewed-By: Ali Ijaz Sheikh ">deps: backport rehash strings after deserialization Jul 28, 2017
doc Reviewed-By: James M Snell ">doc: cross-link util.TextDecoder and intl.md Jul 27, 2017
lib Reviewed-By: Anna Henningsen Reviewed-By: Jeremiah Senkpiel ">repl: do not consider `...` as a REPL command Jul 29, 2017
src Reviewed-By: Andreas Madsen Reviewed-By: Colin Ihrig Reviewed-By: James M Snell Reviewed-By: Tobias Nießen Reviewed-By: Rich Trott ">async_hooks: remove deprecated APIs Jul 27, 2017
test Reviewed-By: Anna Henningsen Reviewed-By: Jeremiah Senkpiel ">repl: do not consider `...` as a REPL command Jul 29, 2017
tools Reviewed-By: Refael Ackermann ">build,test: run v8 tests on windows Jul 27, 2017
.editorconfig Reviewed-By: Roman Reiss Reviewed-By: Michaël Zasso Reviewed-By: Gibson Fahnestock ">tools: disallow trailing whitespace for markdown Nov 21, 2016
.eslintignore Reviewed-By: Anna Henningsen Reviewed-By: Evan Lucas Reviewed-By: Colin Ihrig Reviewed-By: Jeremiah Senkpiel Reviewed-By: Tobias Nießen Reviewed-By: Khaidi Chu ">test: remove disabled tests directory Jul 29, 2017
.eslintrc.yaml Reviewed-By: Yuta Hiroto Reviewed-By: Colin Ihrig Reviewed-By: Evan Lucas Reviewed-By: Timothy Gu Reviewed-By: Luigi Pinca Reviewed-By: James M Snell Reviewed-By: Refael Ackermann Reviewed-By: Alexey Orlenko ">tools: enable stricter linting in lib directory Jul 24, 2017
.gitattributes src: limit .gitattributes eol to vcbuild.bat Jan 13, 2015
.gitignore Reviewed-By: Ben Noordhuis Reviewed-By: James M Snell Reviewed-By: Michael Dawson ">gitignore: add libuv book and GitHub template Jun 7, 2017
.mailmap Reviewed-By: James M Snell Reviewed-By: Refael Ackermann ">meta: update authors list Apr 25, 2017
.remarkrc Reviewed-By: Ben Noordhuis Reviewed-By: Ilkka Myller Reviewed-By: James M Snell ">doc: enable no-file-name-articles remark-lint rule Sep 27, 2016
AUTHORS Reviewed-By: James M Snell Reviewed-By: Refael Ackermann ">meta: update authors list Apr 25, 2017
BSDmakefile Reviewed-By: João Reis ">node: rename from io.js to node Aug 23, 2015
BUILDING.md Reviewed-By: Tobias Nießen Reviewed-By: Refael Ackermann Reviewed-By: James M Snell Reviewed-By: Michael Dawson Reviewed-By: Colin Ihrig Reviewed-By: Nikolai Vavilov ">doc: update minimum g++ version to 4.9.4 Jun 15, 2017
CHANGELOG.md 2017-07-20, Version 8.2.1 (Current) Jul 20, 2017
CODE_OF_CONDUCT.md Reviewed-By: Gibson Fahnestock Reviewed-By: Colin Ihrig Reviewed-By: Anna Henningsen ">meta: move the Code of Conduct to TSC repository Apr 17, 2017
COLLABORATOR_GUIDE.md Reviewed-By: Luigi Pinca Reviewed-By: Richard Lau ">doc: add additional useful ci job to list May 19, 2017
CONTRIBUTING.md Reviewed-By: Refael Ackermann Reviewed-By: Gibson Fahnestock Reviewed-By: Brian White ">doc: use HTTPS URL for suggested upstream remote Jun 10, 2017
GOVERNANCE.md Reviewed-By: Ben Noordhuis Reviewed-By: Luigi Pinca Reviewed-By: Sakthipriyan Vairamani Reviewed-By: Michael Dawson Reviewed-By: Michaël Zasso Reviewed-By: Evan Lucas ">doc: emphasize Collaborators in GOVERNANCE.md Jun 6, 2017
LICENSE Reviewed-By: Michael Dawson Reviewed-By: Refael Ackermann ">deps: ICU 59.1 bump May 9, 2017
Makefile Reviewed-By: Ben Noordhuis Reviewed-By: Myles Borins Reviewed-By: Gibson Fahnestock Reviewed-By: James M Snell ">build: codesign tarball binary on macOS Jul 19, 2017
README.md Reviewed-By: Gireesh Punathil Reviewed-By: Timothy Gu Reviewed-By: Anna Henningsen Reviewed-By: Colin Ihrig ">doc: add XadillaX to collaborators Jul 20, 2017
android-configure Reviewed-By: James M Snell ">build: don't create directory for NDK toolchain Mar 22, 2017
common.gypi Reviewed-By: Refael Ackermann ">tools: skip workaround for newer llvm Jul 22, 2017
configure Reviewed-by: Jakob Gruber Reviewed-by: Ulan Degenbaev Commit-Queue: Yang Guo Cr-Commit-Position: refs/heads/master@{#46732} https://github.com/v8/v8/commit/182caaf4a9b94024e47007d426831c024345cb97 Do not track transitions for built-in objects. Objects created during bootstrapping do not need a transition tree except for elements kind transitions. Bug: v8:6596 Change-Id: I237b8b2792f201336e1c9731c815095dd06bc182 Reviewed-on: https://chromium-review.googlesource.com/571750 Reviewed-by: Igor Sheludko Commit-Queue: Yang Guo Cr-Commit-Position: refs/heads/master@{#46693} Fixes: https://github.com/nodejs/node/issues/14171 PR-URL: https://github.com/nodejs/node/pull/14345 Reviewed-By: Refael Ackermann Reviewed-By: Ben Noordhuis Reviewed-By: Ali Ijaz Sheikh ">deps: backport rehash strings after deserialization Jul 28, 2017
node.gyp Reviewed-By: James M Snell Reviewed-By: Michaël Zasso Reviewed-By: Nikolai Vavilov Reviewed-By: XadillaX ">src: replace ASSERT with CHECK Jul 27, 2017
node.gypi Reviewed-By: Benjamin Gruenbaum Reviewed-By: Michael Dawson Reviewed-By: James M Snell ">build: disable -O3 for C++ coverage Apr 13, 2017
vcbuild.bat Reviewed-By: Refael Ackermann ">build,test: run v8 tests on windows Jul 27, 2017

README.md

Node.js

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. The Node.js package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

The Node.js project is supported by the Node.js Foundation. Contributions, policies, and releases are managed under an open governance model.

This project is bound by a Code of Conduct.

If you need help using or installing Node.js, please use the nodejs/help issue tracker.

Table of Contents

Resources for Newcomers

Official Resources

Unofficial Resources

Please note that unofficial resources are neither managed by (nor necessarily endorsed by) the Node.js TSC/CTC. Specifically, such resources are not currently covered by the Node.js Moderation Policy and the selection and actions of resource operators/moderators are not subject to TSC/CTC oversight.

Release Types

The Node.js project maintains multiple types of releases:

  • Current: Released from active development branches of this repository, versioned by SemVer and signed by a member of the Release Team. Code for Current releases is organized in this repository by major version number. For example: v4.x. The major version number of Current releases will increment every 6 months allowing for breaking changes to be introduced. This happens in April and October every year. Current release lines beginning in October each year have a maximum support life of 8 months. Current release lines beginning in April each year will convert to LTS (see below) after 6 months and receive further support for 30 months.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every second Current release line (major version) will become an LTS line and receive 18 months of Active LTS support and a further 12 months of Maintenance. LTS release lines are given alphabetically ordered codenames, beginning with v4 Argon. LTS releases are less frequent and will attempt to maintain consistent major and minor version numbers, only incrementing patch version numbers. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Versions of code in this repository on the current Current branch, automatically built every 24-hours where changes exist. Use with caution.

More information can be found in the LTS README.

Download

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

Current and LTS Releases

Current and LTS releases are available at https://nodejs.org/download/release/, listed under their version strings. The latest directory is an alias for the latest Current release. The latest LTS release from an LTS line is available in the form: latest-codename. For example: https://nodejs.org/download/release/latest-argon

Nightly Releases

Nightly builds are available at https://nodejs.org/download/nightly/, listed under their version string which includes their date (in UTC time) and the commit SHA at the HEAD of the release.

API Documentation

API documentation is available in each release and nightly directory under docs. https://nodejs.org/api/ points to the API documentation of the latest stable version.

Verifying Binaries

Current, LTS and Nightly download directories all contain a SHASUM256.txt file that lists the SHA checksums for each file available for download.

The SHASUM256.txt can be downloaded 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 -

(Where "node-vx.y.z.tar.gz" is the name of the file you have downloaded)

Additionally, Current and LTS releases (not Nightlies) have GPG signed copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use gpg to verify that the file has not been tampered with.

To verify a SHASUM256.txt.asc, you will first need to import all of the GPG keys of individuals authorized to create releases. They are listed at the bottom of this README under Release Team. Use a command such as this 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)

You can then use gpg --verify SHASUMS256.txt.asc to verify that the file has been signed by an authorized member of the Node.js team.

Once verified, use the SHASUMS256.txt.asc file to get the checksum for the binary verification command above.

Building Node.js

See BUILDING.md for instructions on how to build Node.js from source. The document also contains a list of officially supported platforms.

Security

All security bugs in Node.js are taken seriously and should be reported by emailing security@nodejs.org. This will be delivered to a subset of the project team who handle security issues. Please don't disclose security bugs publicly until they have been handled by the security team.

Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.

Current Project Team Members

The Node.js project team comprises a group of core collaborators and a sub-group that forms the Core Technical Committee (CTC) which governs the project. For more information about the governance of the Node.js project, see GOVERNANCE.md.

CTC (Core Technical Committee)

CTC Emeriti

Collaborators

Collaborators follow the COLLABORATOR_GUIDE.md in maintaining the Node.js project.

Release Team

Node.js releases are signed with one of the following GPG keys:

The full set of trusted release keys can be imported by running:

gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
gpg --keyserver pool.sks-keyservers.net --recv-keys 56730D5401028683275BD23C23EFEFE93C4CFFFE

See the section above on Verifying Binaries for details on what to do with these keys to verify that a downloaded file is official.

Previous releases may also have been signed with one of the following GPG keys:

Working Groups

Information on the current Node.js Working Groups can be found in the CTC repository.