node

JavaScript 언어로 만든 웹 서버, 리눅스 관련 프로젝트예요. 전 세계 개발자 12.3만 명이 스타(좋아요)를 눌렀어요. 깃허브에 올라온 설치파일이 없는 개발자용 프로젝트예요. 마지막 수정은 오늘이에요.

👩‍💻 개발자용⭐ 12.3만 웹 서버리눅스윈도우

원문 소개: Node.js JavaScript runtime ✨🐢🚀✨

바로 쓰기

내 상황에 맞는 방법을 하나 고르세요.

깃허브에는 설치파일이 없어요. 앱으로 배포하는 프로젝트라면 공식 사이트에서 받을 수 있는지 확인해 보세요.

브라우저에서 바로 열기 · 설치 없음

📝 코드 둘러보기github.dev · 무료 ☁️ 클라우드에서 실행Codespaces · 로그인 필요 ⚡ 웹에서 실행StackBlitz · 무료

내 것으로 가져오기

깃허브에서 보기 📦 ZIP 다운로드 🍴 포크(내 계정에 복사) ⭐ 스타 누르러 가기
git clone https://github.com/nodejs/node.git

git clone: 개발자가 코드를 받는 명령어예요. 수정 내역까지 함께 받아져요.

한눈에 보기

인기⭐ 123,388 스타 · 🍴 38,735 포크
무료 여부NOASSERTION
별도 조건이 있는 라이선스예요. 상업용으로 쓰기 전 LICENSE 파일을 확인하세요.
만든 언어JavaScript
최신 버전v26.13.0 · 2026년 10월 29일
활동만든 날 2014.11.27 · 최근 수정 오늘 · 열린 이슈(질문) 1,319개
공식 사이트nodejs.org

설명서 (README)

만든 사람이 쓴 원문 설명서예요. 영어가 어렵다면 한국어로 번역해서 보기 →

Node.js

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

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

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

Contributors are expected to act in a collaborative manner to move the project forward. We encourage the constructive exchange of contrary opinions and compromise. The TSC reserves the right to limit or block contributors who repeatedly act in ways that discourage, exhaust, or otherwise negatively affect other participants.

This project has a Code of Conduct.

Table of contents

Support

Looking for help? Check out the instructions for getting support.

Release types

Node.js follows semantic versioning.

  • Alpha: Under active development where semver-major changes are allowed. Each October, a new release line (for example, Node.js 27) branches off main and receives Alpha releases (for example, 27.0.0-alpha.0.0.0) for 6 months, then are promoted to Current (see below) each April. Alpha releases are signed, tagged, and tested through CITGM, but their API and ABI may change between releases. They are intended for library authors and CI pipelines, not for production use.
  • Current: Under active development, no semver-major changes allowed. Node.js releases a new major version once a year, in April. Releases stay Current for 6 months, then convert to LTS (see below) each October. Their ABI may change between releases. They are intended for library authors and CI pipelines, not for production use.
  • LTS: Releases under Long Term Support, with a focus on stability and security. Only changes that have been on Alpha or Current release for two weeks can be backported to a typical LTS release. Every major version becomes an LTS release, and receives 30 months of LTS support, for a total of 36 months from its first Current release to End-of-Life. LTS release lines have alphabetically-ordered code names, beginning with Node.js 4 Argon.
  • Nightly: Code from the main branch built every 24-hours when there are changes. Unlike Alpha releases, nightly builds are automated and untested. Use with caution.

Release lines up to and including Node.js 26 follow the previous schedule, where a new major version was released every 6 months and only even-numbered major versions became LTS. See the Node.js release schedule announcement for details.

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-hydrogen directory 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 like v22.0.0-nightly20240424ddd0a9e494.

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.asc file with SHA checksums for the files and the releaser PGP signature.

You can get a trusted keyring from nodejs/release-keys, e.g. using curl:

curl -fsLo "/path/to/nodejs-keyring.kbx" "https://github.com/nodejs/release-keys/raw/HEAD/gpg/pubring.kbx"

Alternatively, you can import the releaser keys in your default keyring, see Release keys for commands on how to do that.

Then, you can verify the files you've downloaded locally (if you're using your default keyring, pass --keyring="${GNUPGHOME:-~/.gnupg}/pubring.kbx"):

curl -fsO "https://nodejs.org/dist/${VERSION}/SHASUMS256.txt.asc" \
&& gpgv --keyring="/path/to/nodejs-keyring.kbx" --output SHASUMS256.txt < SHASUMS256.txt.asc \
&& shasum --check SHASUMS256.txt --ignore-missing

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.

Contributing to Node.js

Current project team members

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

TSC (Technical Steering Committee)

TSC voting members

TSC regular members

TSC emeriti members

TSC emeriti members

Collaborators

Emeriti

Collaborator emeriti

Collaborators follow the Collaborator Guide in maintaining the Node.js project.

Triagers

Triagers follow the Triage Guide when responding to new issues.

Release keys

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

You can use the keyring the project maintains at https://github.com/nodejs/release-keys/raw/refs/heads/main/gpg-only-active-keys/pubring.kbx. Alternatively, you can import them from a public key server. Have in mind that the project cannot guarantee the availability of the server nor the keys on that server.

gpg --keyserver hkps://keys.openpgp.org --recv-keys 5BE8A3F6C8A5C01D106C0AD820B1A390B168D356 # Antoine du Hamel
gpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7 # Juan José Arboleda
gpg --keyserver hkps://keys.openpgp.org --recv-keys CC68F5A3106FF448322E48ED27F5E38D5B0A215F # Marco Ippolito
gpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4 # Rafael Gonzaga
gpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C # Richard Lau
gpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A # Ruy Adorno
gpg --keyserver hkps://keys.openpgp.org --recv-keys 655F3B5C1FB3FA8D1A0CA6BDE4A7D232B936D2FD # Stewart X Addison
gpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0 # Ulises Gascón

See Verifying binaries for how to use these keys to verify a downloaded file.

Other keys used to sign some previous releases

The project maintains a keyring able to verify all past releases of Node.js at https://github.com/nodejs/release-keys/raw/refs/heads/main/gpg/pubring.kbx.

Security release stewards

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

License

Node.js is licensed under the MIT License.

This project also depends on external libraries that may use different open-source licenses. For a complete list of included licenses, please see the LICENSE file.

If you are contributing documentation or source changes, please ensure your additions comply with the project’s license guidelines.

자주 묻는 질문

node 무료로 쓸 수 있나요?

네, NOASSERTION 라이선스로 공개된 오픈소스예요. 별도 조건이 있는 라이선스예요. 상업용으로 쓰기 전 LICENSE 파일을 확인하세요. 깃허브 저장소에서 누구나 내려받을 수 있어요.

node 설치는 어떻게 하나요?

따로 설치파일이 없어서 README 설명서의 안내를 따라 설치해야 해요. ZIP 다운로드로 전체 코드를 받거나, 브라우저에서 바로 열어 코드를 둘러볼 수 있어요.

코딩을 몰라도 node 쓸 수 있나요?

조금 어려울 수 있어요. 완성된 설치파일이 없는 개발자용 프로젝트라서 터미널 명령어나 개발 환경이 필요해요. 처음이라면 Codespaces로 브라우저에서 먼저 실행해 보세요.

node 인기는 어느 정도인가요?

깃허브 스타 123,388개, 포크 38,735개를 받은 프로젝트예요. 2014년에 만들어졌고 마지막 수정은 오늘이에요. 스타가 1만 개를 넘으면 전 세계적으로 검증된 인기 프로젝트로 봐요.

복사했어요