close
The Wayback Machine - https://web.archive.org/web/20190417000251/https://github.com/nodejs/node
Skip to content

/node

Node.js JavaScript runtime ✨🐢🚀✨
nodejs javascript node js runtime mit linux macos windows
  1. JavaScript 55.1%
  2. C++ 22.1%
  3. Python 17.0%
  4. C 3.1%
  5. HTML 1.2%
  6. Makefile 0.3%
  7. Other 1.2%
Branch: master
Find File
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching Xcode...

If nothing happens, download Xcode and try again.

Launching Visual Studio...

If nothing happens, download the GitHub extension for Visual Studio and try again.

@Trott
Trott dns: do not indicate invalid IPs are IPv6 
In lib/dns.js, use `isIP()` instead of `isIPv4()` for determining the
`family` property in `lookup()`. If an invalid IP address is returned,
the `family` currently provided is `6`. With this change, it will be
`0`. Update documentation to reflect this.

PR-URL: #27081
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Latest commit 09cdc37 Apr 16, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github doc: add multiple issue templates for GitHub Aug 12, 2018
benchmark benchmark: fix http headers benchmark Apr 11, 2019
deps deps: upgrade npm to 6.9.0 Apr 7, 2019
doc dns: do not indicate invalid IPs are IPv6 Apr 16, 2019
lib dns: do not indicate invalid IPs are IPv6 Apr 16, 2019
src tools: implement mkcodecache as an executable Apr 16, 2019
test build: run `mkcodecache` as an action Apr 16, 2019
tools tools: refactor mkcodecache Apr 16, 2019
.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: unify .editorconfig rules for 2-space Oct 1, 2018
.eslintignore test: run eslint on test file and fix errors Dec 15, 2018
.eslintrc.js lib: remove `env: node` in eslint config for lib files Apr 6, 2019
.flake8 tools: python: ignore instead of select flake8 rules Apr 14, 2019
.gitattributes src: limit .gitattributes eol to vcbuild.bat Jan 13, 2015
.gitignore build,win: put all compilation artifacts into `out` Apr 12, 2019
.mailmap doc: update AUTHORS list Mar 5, 2019
.nycrc test: fix tests that fail under coverage May 22, 2018
.travis.yml meta: travis: run compilation jobs first Apr 15, 2019
AUTHORS doc: update AUTHORS list Mar 5, 2019
BSDmakefile node: rename from io.js to node Aug 23, 2015
BUILDING.md doc: standardize on End-of-Life capitalization Mar 6, 2019
CHANGELOG.md 2019-04-16, Version 8.16.0 'Carbon' (LTS) Apr 16, 2019
CODE_OF_CONDUCT.md doc: simplify CODE_OF_CONDUCT.md Nov 2, 2018
COLLABORATOR_GUIDE.md doc: remove "How is an LTS release cut?" section Mar 30, 2019
CONTRIBUTING.md doc: streamline CONTRIBUTING.md Nov 5, 2018
CPP_STYLE_GUIDE.md doc: fix heading in cpp style guide Jan 7, 2019
GOVERNANCE.md doc: revise TSC Meetings material in GOVERNANCE.md Apr 15, 2019
LICENSE v8: integrate node-heapdump into core Mar 13, 2019
Makefile build: run `mkcodecache` as an action Apr 16, 2019
README.md meta: move ofrobots to TSC emeritus Apr 4, 2019
SECURITY.md doc: add SECURITY.md to readme.md Nov 4, 2018
android-configure build: don't create directory for NDK toolchain Mar 22, 2017
common.gypi build,win: put all compilation artifacts into `out` Apr 12, 2019
configure build: move meta-shebang back to `configure` Sep 7, 2018
configure.py build: run `mkcodecache` as an action Apr 16, 2019
node.gyp build: run `mkcodecache` as an action Apr 16, 2019
node.gypi build: run `mkcodecache` as an action Apr 16, 2019
vcbuild.bat build: run `mkcodecache` as an action Apr 16, 2019

README.md

Node.js

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. For more information on using Node.js, see the Node.js Website.

The Node.js project uses an open governance model. The Node.js Foundation provides support for the project.

This project is bound by a Code of Conduct.

Table of Contents

Support

Node.js contributors have limited availability to address general support questions. Please make sure you are using a currently-supported version of Node.js.

When looking for support, please first search for your question in these venues:

If you didn't find an answer in the resources above, try these unofficial resources:

GitHub issues are for tracking enhancements and bugs, not general support.

The open source license grants you the freedom to use Node.js. It does not guarantee commitments of other people's time. Please be respectful and manage your expectations.

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 18 months of Active LTS support and a further 12 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 time) 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.

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.md 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 pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver pool.sks-keyservers.net --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
gpg --keyserver pool.sks-keyservers.net --recv-keys 77984A986EBC2AA786BC0F66B01FBB92821C587A
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
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

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:

Contributing to Node.js

You can’t perform that action at this time.