/http2

Working on an HTTP/2 implementation for Node.js Core
  1. JavaScript 57.7%
  2. C++ 25.8%
  3. C 5.8%
  4. POV-Ray SDL 5.1%
  5. HTML 2.7%
  6. Python 1.2%
  7. Other 1.7%
JavaScript C++ C POV-Ray SDL HTML Python Other
Find file
Latest commit 4af0278 Jan 29, 2017 @addaleax addaleax src: move MaybeStackBuffer instances to ends of structs 
MaybeStackBuffers can be pretty big with lots of unused space,
and trying to gather most of the used space of structs is
cool for CPU cache efficiency.
Permalink
Failed to load latest commit information.
.github meta: modify pull request template for prepending Dec 29, 2016
benchmark benchmark: add ClientRequest creation benchmark Jan 13, 2017
deps http2: current snapshot Jan 13, 2017
doc doc: fix YAML comment Jan 30, 2017
lib lib: remove redefinitions of TLSSocket#disableRenegotiation Jan 30, 2017
src src: move MaybeStackBuffer instances to ends of structs Jan 30, 2017
test test: refactor and fixup test-http2-binding Jan 30, 2017
tools doc: remove duplicate properties bullet in readme Jan 13, 2017
.editorconfig tools: disallow trailing whitespace for markdown Nov 21, 2016
.eslintignore benchmark: don't lint autogenerated modules Jan 12, 2017
.eslintrc assert, tools: enforce strict (not)equal in eslint Jan 11, 2017
.gitattributes src: limit .gitattributes eol to vcbuild.bat Jan 13, 2015
.gitignore meta: whitelist dotfiles in .gitignore Dec 5, 2016
.mailmap doc: update authors list Sep 4, 2016
.remarkrc doc: enable no-file-name-articles remark-lint rule Sep 27, 2016
AUTHORS doc: update authors list Sep 4, 2016
BSDmakefile node: rename from io.js to node Aug 23, 2015
BUILDING.md doc: correct vcbuild options for windows testing Jan 10, 2017
CHANGELOG.md 2017-01-05, Version 6.9.4 'Boron' (LTS) Jan 5, 2017
CODE_OF_CONDUCT.md doc: enable first-heading-level remark-lint rule Sep 27, 2016
COLLABORATOR_GUIDE.md doc: update LTS info for current releases Jan 10, 2017
CONTRIBUTING.md doc: correct vcbuild options for windows testing Jan 10, 2017
GOVERNANCE.md doc: update minute-taking procedure for CTC Nov 6, 2016
LICENSE deps: Intl: ICU 58 bump: configure/LICENSE/docs Oct 31, 2016
Makefile build: fix node_g target Dec 7, 2016
README.md doc: add joyeecheung to collaborators Jan 4, 2017
ROADMAP.md tools: enable more remark-lint rules Sep 25, 2016
WORKING_GROUPS.md meta: decharter the http working group Jan 6, 2017
android-configure build: update android-configure script for npm Apr 22, 2016
common.gypi build: use wxneeded on openbsd Oct 28, 2016
configure http2: current snapshot Jan 13, 2017
node.gyp Working on round 9 Jan 24, 2017
vcbuild.bat build: change nosign flag to sign and flips logic Dec 18, 2016

README.md

Node.js

Gitter CII Best Practices

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.

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

Download

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.

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.

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)

Collaborators

Collaborators (which includes CTC members) follow the COLLABORATOR_GUIDE.md in maintaining the Node.js project.

Release Team

Releases of Node.js and io.js will be 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 9554F04D7259F04124DE6B476D5A82AC7E37093B
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

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 of Node.js have been signed with one of the following GPG keys:

  • Isaac Z. Schlueter <i@izs.me> 93C7E9E91B49E432C2F75674B0A78B0A6C481CF6
  • Julien Gilli <jgilli@fastmail.fm> 114F43EE0176B71C7BC219DD50A3051F888C628D
  • Timothy J Fontaine <tjfontaine@gmail.com> 7937DFD2AB06298B2293C3187D33FF9D0246406D