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. We are also bound by a Code of Conduct.
If you need help using or installing Node.js, please use the nodejs/help issue tracker.
- Website
- Node.js Help
- Contributing to the project
- IRC (node core development): #node-dev on chat.freenode.net
- IRC (general questions): #node.js on chat.freenode.net. Please see
https://nodeirc.info/ for more information regarding the
#node.js
IRC channel.
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.
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. More information can be found in the LTS README.
- Nightly: Versions of code in this repository on the current Current branch, automatically built every 24-hours where changes exist. Use with caution.
Binaries, installers, and source tarballs are available at https://nodejs.org.
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 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 is available in each release and nightly directory under docs. https://nodejs.org/api/ points to the API documentation of the latest stable version.
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.
See BUILDING.md for instructions on how to build Node.js from source.
All security bugs in Node.js are taken seriously and should be reported by emailing [email protected]. 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.
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.
- addaleax - Anna Henningsen <[email protected]> (she/her)
- bnoordhuis - Ben Noordhuis <[email protected]>
- ChALkeR - Сковорода Никита Андреевич <[email protected]> (he/him)
- cjihrig - Colin Ihrig <[email protected]>
- evanlucas - Evan Lucas <[email protected]> (he/him)
- fhinkel - Franziska Hinkelmann <[email protected]>
- fishrock123 - Jeremiah Senkpiel <[email protected]>
- indutny - Fedor Indutny <[email protected]>
- jasnell - James M Snell <[email protected]> (he/him)
- mhdawson - Michael Dawson <[email protected]> (he/him)
- misterdjules - Julien Gilli <[email protected]>
- mscdex - Brian White <[email protected]>
- MylesBorins - Myles Borins <[email protected]> (he/him)
- ofrobots - Ali Ijaz Sheikh <[email protected]>
- rvagg - Rod Vagg <[email protected]>
- shigeki - Shigeki Ohtsu <[email protected]> (he/him)
- targos - Michaël Zasso <[email protected]> (he/him)
- thefourtheye - Sakthipriyan Vairamani <[email protected]> (he/him)
- trevnorris - Trevor Norris <[email protected]>
- Trott - Rich Trott <[email protected]> (he/him)
- abouthiroppy - Yuta Hiroto <[email protected]> (he/him)
- ak239 - Aleksei Koziatinskii <[email protected]>
- andrasq - Andras <[email protected]>
- AndreasMadsen - Andreas Madsen <[email protected]> (he/him)
- bengl - Bryan English <[email protected]> (he/him)
- benjamingr - Benjamin Gruenbaum <[email protected]>
- bmeck - Bradley Farias <[email protected]>
- brendanashworth - Brendan Ashworth <[email protected]>
- bzoz - Bartosz Sosnowski <[email protected]>
- calvinmetcalf - Calvin Metcalf <[email protected]>
- chrisdickinson - Chris Dickinson <[email protected]>
- claudiorodriguez - Claudio Rodriguez <[email protected]>
- danbev - Daniel Bevenius <[email protected]>
- edsadr - Adrian Estrada <[email protected]> (he/him)
- eljefedelrodeodeljefe - Robert Jefe Lindstaedt <[email protected]>
- estliberitas - Alexander Makarenko <[email protected]>
- eugeneo - Eugene Ostroukhov <[email protected]>
- firedfox - Daniel Wang <[email protected]>
- geek - Wyatt Preul <[email protected]>
- gibfahn - Gibson Fahnestock <[email protected]> (he/him)
- iarna - Rebecca Turner <[email protected]>
- imyller - Ilkka Myller <[email protected]>
- isaacs - Isaac Z. Schlueter <[email protected]>
- italoacasas - Italo A. Casas <[email protected]> (he/him)
- iWuzHere - Imran Iqbal <[email protected]>
- JacksonTian - Jackson Tian <[email protected]>
- jbergstroem - Johan Bergström <[email protected]>
- jhamhader - Yuval Brik <[email protected]>
- joaocgreis - João Reis <[email protected]>
- joshgav - Josh Gavant <[email protected]>
- joyeecheung - Joyee Cheung <[email protected]> (she/her)
- julianduque - Julian Duque <[email protected]> (he/him)
- JungMinu - Minwoo Jung <[email protected]> (he/him)
- lance - Lance Ball <[email protected]>
- lpinca - Luigi Pinca <[email protected]> (he/him)
- lxe - Aleksey Smolenchuk <[email protected]>
- matthewloring - Matthew Loring <[email protected]>
- mcollina - Matteo Collina <[email protected]> (he/him)
- micnic - Nicu Micleușanu <[email protected]> (he/him)
- mikeal - Mikeal Rogers <[email protected]>
- monsanto - Christopher Monsanto <[email protected]>
- not-an-aardvark - Teddy Katz <[email protected]>
- Olegas - Oleg Elifantiev <[email protected]>
- orangemocha - Alexis Campailla <[email protected]>
- othiym23 - Forrest L Norvell <[email protected]> (he/him)
- petkaantonov - Petka Antonov <[email protected]>
- phillipj - Phillip Johnsen <[email protected]>
- piscisaureus - Bert Belder <[email protected]>
- pmq20 - Minqi Pan <[email protected]>
- princejwesley - Prince John Wesley <[email protected]>
- qard - Stephen Belanger <[email protected]> (he/him)
- richardlau - Richard Lau <[email protected]>
- rlidwka - Alex Kocharin <[email protected]>
- rmg - Ryan Graham <[email protected]>
- robertkowalski - Robert Kowalski <[email protected]>
- romankl - Roman Klauke <[email protected]>
- ronkorving - Ron Korving <[email protected]>
- RReverser - Ingvar Stepanyan <[email protected]>
- saghul - Saúl Ibarra Corretgé <[email protected]>
- sam-github - Sam Roberts <[email protected]>
- santigimeno - Santiago Gimeno <[email protected]>
- seishun - Nikolai Vavilov <[email protected]>
- silverwind - Roman Reiss <[email protected]>
- srl295 - Steven R Loomis <[email protected]>
- stefanmb - Stefan Budeanu <[email protected]>
- tellnes - Christian Tellnes <[email protected]>
- thekemkid - Glen Keane <[email protected]> (he/him)
- thlorenz - Thorsten Lorenz <[email protected]>
- TimothyGu - Timothy Gu <[email protected]> (he/him)
- tunniclm - Mike Tunnicliffe <[email protected]>
- vkurchatkin - Vladimir Kurchatkin <[email protected]>
- vsemozhetbyt - Vse Mozhet Byt <[email protected]> (he/him)
- watilde - Daijiro Wachi <[email protected]> (he/him)
- whitlockjc - Jeremy Whitlock <[email protected]>
- yorkie - Yorkie Liu <[email protected]>
- yosuke-furukawa - Yosuke Furukawa <[email protected]>
Collaborators (which includes CTC members) follow the COLLABORATOR_GUIDE.md in maintaining the Node.js project.
Node.js releases are signed with one of the following GPG keys:
- Colin Ihrig <[email protected]>
94AE36675C464D64BAFA68DD7434390BDBE9B9C5
- Evan Lucas <[email protected]>
B9AE9905FFD7803F25714661B63B535A4C206CA9
- Italo A. Casas <[email protected]>
56730D5401028683275BD23C23EFEFE93C4CFFFE
- James M Snell <[email protected]>
71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
- Jeremiah Senkpiel <[email protected]>
FD3A5288F042B6850C66B31F09FE44734EB7990E
- Myles Borins <[email protected]>
C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
- Rod Vagg <[email protected]>
DD8F2338BAE7501E3DD5AC78C273792F7D83545D
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:
- Chris Dickinson <[email protected]>
9554F04D7259F04124DE6B476D5A82AC7E37093B
- Isaac Z. Schlueter <[email protected]>
93C7E9E91B49E432C2F75674B0A78B0A6C481CF6
- Julien Gilli <[email protected]>
114F43EE0176B71C7BC219DD50A3051F888C628D
- Timothy J Fontaine <[email protected]>
7937DFD2AB06298B2293C3187D33FF9D0246406D
Information on the current Node.js Working Groups can be found in the CTC repository.