OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2026-01-15 12:15:26 +00:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity
40,724 Commits 30 Branches 683 Tags
3e57b93963ffe285e14faa3926e83f9633c98e66
Go to file
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Download ZIP Download TAR.GZ Download BUNDLE
Joyee Cheung 3e57b93963 src: compile code eagerly in snapshot builder 
By default V8 only compiles the top-level function and
skips code generation for inner functions - that would
only be done when those inner functions are invoked.
Since builtins are compiled as wrapped functions, most
functions that look visually top-level are not actually
included in the built-in code cache. For most of the
builtins this is not too bad because usually only a subset of
all builtin functions are needed by a particular
application and including all their code in the binary
would incur an unnecessary size overhead. But there is also
a subset of more commonly used builtins and it would be
better to include the inner functions in the built-in
code cache because they are more universally used by
most applications.

This patch changes the compilation strategy to eager compilation
(including inner functions) for the following scripts:

1. Primordials (internal/per_context/*), in all situations.
2. Bootstrap scripts (internal/bootstrap/*) and main scripts
   (internal/main/*), when being compiled for built-in code
   cache.
3. Any scripts loaded during built-in snapshot generation.

We can't compile the code eagerly during snapshot generation
and include them into the V8 snapshot itself just now because
we need to start the inspector before context deserialization
for coverage collection to work. So leave that as a TODO.

With this patch the binary size increases by about 666KB
(~0.6% increase) in return the worker startup can be 18-19% faster.

PR-URL: https://github.com/nodejs/node/pull/51672
Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io>
2024-02-20 21:40:12 +00:00
.devcontainer
build: fix for VScode "Reopen in Container"
2023-12-31 01:26:30 +00:00
.github
meta: bump codecov/codecov-action from 3.1.4 to 4.0.1
2024-02-04 10:28:07 +00:00
android-patches
build: rewritten the Android build system
2022-09-12 08:10:29 +00:00
benchmark
lib: enable WebSocket by default
2024-02-04 14:03:39 +00:00
deps
deps: update timezone to 2024a
2024-02-15 19:46:31 +00:00
doc
doc,crypto: further clarify RSA_PKCS1_PADDING support
2024-02-20 10:23:54 -05:00
lib
lib: create global console properties at snapshot build time
2024-02-20 18:25:31 +00:00
src
src: compile code eagerly in snapshot builder
2024-02-20 21:40:12 +00:00
test
test: skip test-http-correct-hostname on loong64
2024-02-20 10:51:14 -05:00
tools
build: encode non-ASCII Latin1 characters as one byte in JS2C
2024-02-17 17:09:24 +00:00
typings
async_hooks,inspector: implement inspector api without async_wrap
2024-01-24 13:29:28 +00:00
.clang-format
…
.cpplint
…
.editorconfig
…
.eslintignore
esm: use import attributes instead of import assertions
2023-10-14 03:52:38 +00:00
.eslintrc.js
esm: use import attributes instead of import assertions
2023-10-14 03:52:38 +00:00
.gitattributes
build: add .gitattributes for npm and other shims
2022-07-19 21:27:49 +01:00
.gitignore
meta: add .temp and .lock tags to ignore
2024-01-04 19:01:42 +00:00
.gitpod.yml
doc,tools: switch to @node-core/utils
2023-09-25 11:48:03 +00:00
.mailmap
meta: add .mailmap entry for lemire
2024-01-29 22:09:16 +00:00
.nycrc
…
.yamllint.yaml
…
android_configure.py
zlib: fix discovery of cpu-features.h for android
2023-09-29 11:52:46 -04:00
android-configure
build: add python 3.11 support for android
2022-12-11 02:58:02 +00:00
BSDmakefile
…
BUILD.gn
build: add GN build files
2023-11-11 09:51:05 +00:00
BUILDING.md
doc: bump FreeBSD experimental support to 13.2
2023-12-22 09:26:09 +00:00
CHANGELOG.md
2024-02-14, Version 21.6.2 (Current)
2024-02-14 14:12:25 -03:00
CODE_OF_CONDUCT.md
…
codecov.yml
tools: disable Codecov commit statuses
2023-04-01 07:08:22 +00:00
common.gypi
deps: V8: cherry-pick efb1133eb894
2024-02-01 11:53:59 +00:00
configure
build: support Python 3.12
2023-11-06 14:11:01 +00:00
configure.py
build: build opt to set local location of headers
2024-02-15 16:41:37 -05:00
CONTRIBUTING.md
…
glossary.md
…
GOVERNANCE.md
meta: clarify nomination process according to Node.js charter
2023-11-26 17:14:19 +00:00
LICENSE
doc: the GN files should use Node's license
2023-12-28 20:27:05 +00:00
Makefile
build: run embedtest using node executable
2023-09-18 00:06:20 +02:00
node.gni
build: remove copyright header in node.gni
2024-01-24 02:11:08 +00:00
node.gyp
build: encode non-ASCII Latin1 characters as one byte in JS2C
2024-02-17 17:09:24 +00:00
node.gypi
src: fix dynamically linked zlib version
2023-12-04 17:30:58 +00:00
onboarding.md
doc,tools: switch to @node-core/utils
2023-09-25 11:48:03 +00:00
pyproject.toml
tools: skip ruff on tools/gyp
2023-10-31 12:44:37 +00:00
README.md
doc: add zcbenz to collaborators
2024-02-20 20:51:48 +09:00
SECURITY.md
doc: mention node:wasi in the Threat Model
2023-12-21 12:55:52 +00:00
tsconfig.json
lib: fix internalBinding typings
2023-09-23 10:48:34 +00:00
unofficial.gni
doc: the GN files should use Node's license
2023-12-28 20:27:05 +00:00
vcbuild.bat
build: check before removing %config% link
2024-01-25 20:46:09 +00:00

README.md

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

  • Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v19.x). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life 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 stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 12 months of Active LTS support and a further 18 months of Maintenance. 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 are changes. Use with caution.

Current and LTS releases follow semantic versioning. A member of the Release Team signs each Current and LTS release. 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 name and filename contains a date (in UTC) and the commit SHA at the HEAD of the release.

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 file with SHA checksums for the files.

To download SHASUMS256.txt 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 -

For Current and LTS, the GPG detached signature of SHASUMS256.txt is in SHASUMS256.txt.sig. You can use it with gpg to verify the integrity of SHASUMS256.txt. You will first need to import the GPG keys of individuals authorized to create releases. To import the keys:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C

See Release keys for a script to import active release keys.

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

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

Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify the file's signature.

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):

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

gpg --keyserver hkps://keys.openpgp.org --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver hkps://keys.openpgp.org --recv-keys 141F07595B7B3FFE74309A937405533BE57C7D57
gpg --keyserver hkps://keys.openpgp.org --recv-keys 74F12602B6F1C4E913FAA37AD3A89613643B6201
gpg --keyserver hkps://keys.openpgp.org --recv-keys DD792F5973C6DE52C432CBDAC77ABFA00DDBF2B7
gpg --keyserver hkps://keys.openpgp.org --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver hkps://keys.openpgp.org --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver hkps://keys.openpgp.org --recv-keys 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4
gpg --keyserver hkps://keys.openpgp.org --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C
gpg --keyserver hkps://keys.openpgp.org --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A
gpg --keyserver hkps://keys.openpgp.org --recv-keys A363A499291CBBC940DD62E41F10027AF002F8B0

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

Other keys used to sign some previous releases

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 available under the MIT license. Node.js also includes external libraries that are available under a variety of licenses. See LICENSE for the full license text.

Reference in New Issue View Git Blame Copy Permalink
Description
Node.js JavaScript runtime ✨🐢🚀✨ nodejs.org
Readme Multiple Licenses 1.4 GiB
Languages
JavaScript 62.4%
C++ 23.1%
Python 10.1%
C 2.7%
HTML 0.6%
Other 0.9%