Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up

Node.js JavaScript runtime ✨🐢🚀✨

License

NotificationsYou must be signed in to change notification settings

nodejs/node

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Node.js is an open-source, cross-platform JavaScript runtime environment.

For information on using Node.js, see theNode.js website.

The Node.js project uses anopen governance model. TheOpenJS Foundation provides support for the project.

Contributors are expected to act in a collaborative manner to movethe project forward. We encourage the constructive exchange of contraryopinions and compromise. TheTSCreserves the right to limit or block contributors who repeatedly act in waysthat discourage, exhaust, or otherwise negatively affect other participants.

This project has aCode of Conduct.

Table of contents

Support

Looking for help? Check out theinstructions for getting support.

Release types

  • Current: Under active development. Code for the Current release is in thebranch for its major version number (for example,v22.x). Node.js releases a newmajor version every 6 months, allowing for breaking changes. This happens inApril and October every year. Releases appearing each October have a supportlife 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 stabilityand security. Every even-numbered major version will become an LTS release.LTS releases receive 12 months ofActive LTS support and a further 18 monthsofMaintenance. LTS release lines have alphabetically-ordered code names,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 arechanges. Use with caution.

Current and LTS releases followsemantic versioning. Amember of the Release Teamsigns each Current and LTS release.For more information, see theRelease README.

Download

Binaries, installers, and source tarballs are available athttps://nodejs.org/en/download/.

Current and LTS releases

https://nodejs.org/download/release/

Thelatest directory is analias for the latest Current release. The latest-codename directory is analias for the latest release from an LTS line. For example, thelatest-hydrogendirectory contains the latest Hydrogen (Node.js 18) release.

Nightly releases

https://nodejs.org/download/nightly/

Each directory and filename includes the version (e.g.,v22.0.0),followed by the UTC date (e.g.,20240424 for April 24, 2024),and the short commit SHA of the HEAD of the release (e.g.,ddd0a9e494).For instance, a full directory name might look likev22.0.0-nightly20240424ddd0a9e494.

API documentation

Documentation for the latest Current release is athttps://nodejs.org/api/.Version-specific documentation is available in each release directory in thedocs subdirectory. Version-specific documentation is also athttps://nodejs.org/download/docs/.

Verifying binaries

Download directories contain aSHASUMS256.txt file with SHA checksums for thefiles.

To downloadSHASUMS256.txt usingcurl:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt

To check that downloaded files match the checksum, usesha256sum:

sha256sum -c SHASUMS256.txt --ignore-missing

For Current and LTS, the GPG detached signature ofSHASUMS256.txt is inSHASUMS256.txt.sig. You can use it withgpg to verify the integrity ofSHASUMS256.txt. You will first need to importthe GPG keys of individuals authorized to create releases.

SeeRelease keys for commands to import active release keys.

Next, download theSHASUMS256.txt.sig for the release:

curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig

Then usegpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verifythe file's signature.

Building Node.js

SeeBUILDING.md for instructions on how to build Node.js fromsource and a list of supported platforms.

Security

For information on reporting security vulnerabilities in Node.js, seeSECURITY.md.

Contributing to Node.js

Current project team members

For information about the governance of the Node.js project, seeGOVERNANCE.md.

TSC (Technical Steering Committee)

TSC voting members

TSC regular members

TSC emeriti members

TSC emeriti members

Collaborators

Emeriti

Collaborator emeriti

Collaborators follow theCollaborator Guide inmaintaining the Node.js project.

Triagers

Triagers follow theTriage Guide whenresponding to new issues.

Release keys

Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):

To import the full set of trusted release keys (including subkeys possibly usedto sign releases):

gpg --keyserver hkps://keys.openpgp.org --recv-keys C0D6248439F1D5604AAFFB4021D900FFDB233756# Antoine du Hamelgpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7# Juan José Arboledagpg --keyserver hkps://keys.openpgp.org --recv-keys CC68F5A3106FF448322E48ED27F5E38D5B0A215F# Marco Ippolitogpg --keyserver hkps://keys.openpgp.org --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600# Michaël Zassogpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4# Rafael Gonzagagpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C# Richard Laugpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A# Ruy Adornogpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0# Ulises Gascón

SeeVerifying binaries for how to use these keys toverify a downloaded file.

Other keys used to sign some previous releases

Security release stewards

When possible, the commitment to take slots in thesecurity release steward rotation is made by companies in orderto ensure individuals who act as security stewards have thesupport and recognition from their employer to be able toprioritize security releases. Security release stewards manage securityreleases on a rotation basis as outlined in thesecurity release process.

License

Node.js is available under theMIT License. Node.js also includesexternal libraries that are available under a variety of licenses. SeeLICENSE for the fulllicense text.

[8]ページ先頭
©2009-2025 Movatter.jp