Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

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
Appearance settings
forked fromnodejs/node

Node.js JavaScript runtime ✨🐢🚀✨

License

NotificationsYou must be signed in to change notification settings

ChenKaiKe/node

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Node.js

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

The Node.js project is supported by theNode.js Foundation. Contributions,policies, and releases are managed under anopen governance model.

This project is bound by aCode of Conduct.

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

Table of Contents

Resources for Newcomers

Official Resources

Unofficial Resources

Please note that unofficial resources are neither managed by (nor necessarilyendorsed by) the Node.js TSC/CTC. Specifically, such resources are notcurrently covered by theNode.js Moderation Policy and the selection andactions 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 bySemVer and signed by a member of theRelease Team.Code for Current releases is organized in this repository by major versionnumber. For example:v4.x.The major version number of Current releases will increment every 6 monthsallowing for breaking changes to be introduced. This happens in April andOctober every year. Current release lines beginning in October each year havea maximum support life of 8 months. Current release lines beginning in Aprileach year will convert to LTS (see below) after 6 months and receive furthersupport for 30 months.
  • LTS: Releases that receive Long-term Support, with a focus on stabilityand security. Every second Current release line (major version) will become anLTS line and receive 18 months ofActive LTS support and a further 12months ofMaintenance. LTS release lines are given alphabeticallyordered codenames, beginning with v4 Argon. LTS releases are less frequentand will attempt to maintain consistent major and minor version numbers,only incrementing patch version numbers. There are no breaking changes orfeature additions, except in some special circumstances. More informationcan be found in theLTS README.
  • Nightly: Versions of code in this repository on the current Currentbranch, automatically built every 24-hours where changes exist. Use withcaution.

Download

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

Current and LTS Releases

Current andLTS releases are available athttps://nodejs.org/download/release/, listed under their version strings.Thelatest directory is analias for the latest Current release. The latest LTS release from an LTSline is available in the form: latest-codename. For example:https://nodejs.org/download/release/latest-argon

Nightly Releases

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

API Documentation

API documentation is available in each release and nightlydirectory underdocs.https://nodejs.org/api/ points to the APIdocumentation of the latest stable version.

Verifying Binaries

Current, LTS and Nightly download directories all contain aSHASUM256.txtfile that lists the SHA checksums for each file available fordownload.

TheSHASUM256.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, runit throughsha256sum 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 havedownloaded)

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

To verify a SHASUM256.txt.asc, you will first need to import all ofthe GPG keys of individuals authorized to create releases. They arelisted at the bottom of this README underRelease 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 activerelease keys)

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

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

Building Node.js

SeeBUILDING.md for instructions on how to buildNode.js from source. The document also contains a list ofofficially supported platforms.

Security

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

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

Current Project Team Members

The Node.js project team comprises a group of core collaborators and a sub-groupthat forms theCore Technical Committee (CTC) which governs the project. Formore information about the governance of the Node.js project, seeGOVERNANCE.md.

CTC (Core Technical Committee)

CTC Emeriti

Collaborators

Collaborators (which includes CTC members) follow theCOLLABORATOR_GUIDE.md in maintaining the Node.jsproject.

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 94AE36675C464D64BAFA68DD7434390BDBE9B9C5gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990Egpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545Dgpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9gpg --keyserver pool.sks-keyservers.net --recv-keys 56730D5401028683275BD23C23EFEFE93C4CFFFE

See the section above onVerifying Binaries for detailson 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 theCTC repository.

About

Node.js JavaScript runtime ✨🐢🚀✨

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript65.1%
  • C++23.6%
  • C5.4%
  • HTML2.1%
  • POV-Ray SDL1.2%
  • Python1.1%
  • Other1.5%
[8]ページ先頭
©2009-2025 Movatter.jp