Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2025-10-13 08:01
📄 adding-new-napi-api.md # Contributing a new API to Node-API Node-API is the ABI-stable API for native addons. We encourage contributions to enhance the API, while also ensuring compatibility and adherence to guidelines. When adding a new API to Node-API, please follow these principles and guidelines: ## Core principles 1. Adherence to Node-API standards * Must be a C API. * Must not throw exceptions. * Must return `napi_status`. * Should consume `napi_env`. * Must operate on primitive data types, pointers to primitive data types, or opaque handles. * Must be a necessary API, not a convenience API (which belongs in node-addon-api). * Must not break ABI compatibility with other Node.js versions. 2. Maintaining VM agnosticism * New APIs should be compatible with various JavaScript VMs. ## Documentation and testing 1. Documentation * PRs introducing new APIs must include corresponding documentation updates. * Experimental APIs must be clearly documented as experimental and require an explicit compile-time flag to opt-in (`#define`). 2. Testing * PRs must include at least one test case demonstrating API usage. * Should include test cases for various interesting uses of the API. * Should provide a sample demonstrating realistic usage, similar to a real-world addon. ## Process and approval 1. Team discussion * New APIs should be discussed in a Node-API team meeting. 2. Review and approval * A new API addition must be signed off by at least two Node-API team members. * Should be implemented in at least one other VM implementation of Node.js. 3. Experimental phase * New APIs must be marked as experimental for at least one minor Node.js release before promotion. * Must have a feature flag (`NODE_API_EXPERIMENTAL_HAS_<FEATURE>`) for distinguishing experimental feature existence. * Must be considered for backporting. * Exit criteria from experimental status include: * Opening a PR in `nodejs/node` to remove experimental status, tagged as node-api and semver-minor. * Approval by the Node-API team. * Availability of a down-level implementation if backporting is needed. * Usage by a published real-world module. * Implementation in an alternative VM.	2.31 KB	2025-02-28 19:16
📄 adding-v8-fast-api.md # Adding V8 Fast API Node.js uses [V8](https://v8.dev/) as its JavaScript engine. Embedding functions implemented in C++ incur a high overhead, so V8 provides an API to implement native functions which may be invoked directly from JIT-ed code. These functions also come with additional constraints, for example, they may not trigger garbage collection. ## Limitations * Fast API functions may not trigger garbage collection. This means by proxy that JavaScript execution and heap allocation are also forbidden, including `v8::Array::Get()` or `v8::Number::New()`. * Throwing errors is not available from within a fast API call, but can be done through the fallback to the slow API. * Not all parameter and return types are supported in fast API calls. For a full list, please look into [`v8-fast-api-calls.h`](../../deps/v8/include/v8-fast-api-calls.h). ## Requirements * Any function passed to `CFunction::Make`, including fast API function declarations, should have their signature registered in [`node_external_reference.h`](../../src/node_external_reference.h) file. Although, it would not start failing or crashing until the function ends up in a snapshot (either the built-in or a user-land one). Please refer to the [binding functions documentation](../../src#binding-functions) for more information. * To test fast APIs, make sure to run the tests in a loop with a decent iterations count to trigger relevant optimizations that prefer the fast API over the slow one. * The fast callback must be idempotent up to the point where error and fallback conditions are checked, because otherwise executing the slow callback might produce visible side effects twice. ## Fallback to slow path Fast API supports fallback to slow path for when it is desirable to do so, for example, when throwing a custom error or executing JavaScript code is needed. The fallback mechanism can be enabled and changed from the C++ implementation of the fast API function declaration. Passing `true` to the `fallback` option will force V8 to run the slow path with the same arguments. In V8, the options fallback is defined as `FastApiCallbackOptions` inside [`v8-fast-api-calls.h`](../../deps/v8/include/v8-fast-api-calls.h). * C++ land Example of a conditional fast path on C++ ```cpp // Anywhere in the execution flow, you can set fallback and stop the execution. static double divide(const int32_t a, const int32_t b, v8::FastApiCallbackOptions& options) { if (b == 0) { options.fallback = true; return 0; } else { return a / b; } } ``` ## Example A typical function that communicates between JavaScript and C++ is as follows. * On the JavaScript side: ```js const { divide } = internalBinding('custom_namespace'); ``` * On the C++ side: ```cpp #include "v8-fast-api-calls.h" namespace node { namespace custom_namespace { static void SlowDivide(const FunctionCallbackInfo<Value>& args) { Environment* env = Environment::GetCurrent(args); CHECK_GE(args.Length(), 2); CHECK(args[0]->IsInt32()); CHECK(args[1]->IsInt32()); auto a = args[0].As<v8::Int32>(); auto b = args[1].As<v8::Int32>(); if (b->Value() == 0) { return node::THROW_ERR_INVALID_STATE(env, "Error"); } double result = a->Value() / b->Value(); args.GetReturnValue().Set(v8::Number::New(env->isolate(), result)); } static double FastDivide(const int32_t a, const int32_t b, v8::FastApiCallbackOptions& options) { if (b == 0) { options.fallback = true; return 0; } else { return a / b; } } CFunction fast_divide_(CFunction::Make(FastDivide)); static void Initialize(Local<Object> target, Local<Value> unused, Local<Context> context, void* priv) { SetFastMethod(context, target, "divide", SlowDivide, &fast_divide_); } void RegisterExternalReferences(ExternalReferenceRegistry* registry) { registry->Register(SlowDivide); registry->Register(FastDivide); registry->Register(fast_divide_.GetTypeInfo()); } } // namespace custom_namespace } // namespace node NODE_BINDING_CONTEXT_AWARE_INTERNAL(custom_namespace, node::custom_namespace::Initialize); NODE_BINDING_EXTERNAL_REFERENCE( custom_namespace, node::custom_namespace::RegisterExternalReferences); ``` * Update external references ([`node_external_reference.h`](../../src/node_external_reference.h)) Since our implementation used `double(const int32_t a, const int32_t b, v8::FastApiCallbackOptions& options)` signature, we need to add it to external references and in `ALLOWED_EXTERNAL_REFERENCE_TYPES`. Example declaration: ```cpp using CFunctionCallbackReturningDouble = double (*)(const int32_t a, const int32_t b, v8::FastApiCallbackOptions& options); ```	5.06 KB	2025-02-28 19:16
📄 advocacy-ambassador-program.md # Advocacy Ambassador program Node.js aims to support and encourage developers and developer advocates to promote Node.js as a project and to help communicate key messages to their constituencies. The ambassador program does that by: * Maintaining an up-to-date set of messages that the Node.js maintainers would like ambassadors to promote. These will be documented in the nodejs/ambassadors repository. * Maintaining an up-to-date set of topics on which additional content would benefit the community. These will be documented in the nodejs/ambassadors repository. * Providing a space for collaborators to share new topics/features they are working on when they would be happy for ambassadors to help share and get early feedback. * Helping ambassadors promote content that aligns with the messages and topics defined. * Advocating for ambassadors to be part of the OpenJS speakers bureau, even if the ambassador is not otherwise an active member of the project itself. * Each ambassador could add a maximum of three links to resources to learn Node.js on a dedicated page on the main Node.js website. At least one of those must be a free resource. The Node.js TSC members could ask for coupon codes to verify the material if they so decide. ## Ambassadors nominations Any member of the Node.js organization may nominate an ambassador. The Technical Steering Committee (TSC) will review/approve ambassadors. In the initial phase of the program: * There will be a maximum of 4 ambassadors. * The term will be for the calendar year. After a year, ambassadors automatically drop out of the ambassador list and must be re-nominated. * Ambassadors will be documented on the nodejs/ambassadors `README.md`. The TSC may remove an ambassador for any reason, including promoting content misaligned with the project. Members of the Node.js organization can nominate ambassadors by opening a discussion issue with the nomination in [nodejs/collaborators](https://github.com/nodejs/collaborators/) titled `Nomination X to be an Ambassador`, where X is the name of the person being nominated. If there is no objection within 14 days, the nomination is approved. ## Onboarding To onboard an ambassador, a member of the TSC will: * \[ ] Add the ambassador to the nodejs/ambassadors team. * \[ ] Add the ambassador to the nodejs/ambassadors `README.md`. * \[ ] Add the ambassador to the OpenJS Slack channel. ## Reviewing content Ambassadors are asked to share links to new content before asking for the content to be promoted. The goal is to provide the opportunity for collaborators to help improve content as opposed to a detailed nitpick review. This is done by opening an issue in the nodejs/ambassadors repository, which limits access to members of the Node.js organization. The issue may include the link to existing published content or a draft of the content itself. Interested members of the Node.js organization may comment in the issue and the ambassadors are expected to consider those suggestions and update the content when they feel it is appropriate. Explicit approval is not required in the issue (i.e. if there is no input, that's OK), but review comments should be addressed before requesting promotion. ## Expectations on Ambassadors Ambassadors are expected to engage both within the project and externally in a manner that is consistent with the project's [Code of Conduct](https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md) as well as the additional expectations outlined in [Member Expectations](https://github.com/nodejs/admin/blob/main/MemberExpectations.md). ## Promoting content We trust ambassadors to only request promotion of content that lines up with the messages and topics outlined, that this content does not overly market their employer or product/business, and that they have followed the review process. An ambassador can request promotion of content in the following ways: * Requesting that a post be reposted by the Node.js account on a social media platform. * @-mentioning the nodejs/ambassadors team to ask other ambassadors to repost. * Posting a link to the content in the "what's new" issue in nodejs/ambassadors so that it goes out on the news feed. Foundation staff will repost the social media post without any need for validation based on the request coming from an ambassador. These requests can be made through the existing social channel in the OpenJS Slack. For that reason and for communication purposes and collaboration opportunities, ambassadors should be members of the [OpenJS Slack](https://slack-invite.openjsf.org/). ## Messages and topics to promote ### How to add messages or topics to promote Messages or topics that ambassadors are asked to promote are added to this document in the [Current messages for promotion](#current-messages-for-promotion) section through the standard PR process except that they should be open for 7 days before landing and should include and at mention to the nodejs/TSC for awareness. They should be removed through the same process when no longer relevant. ### Current messages for promotion #### Sample message (Leave this one at the top) ##### Goal The goal is to raise awareness of XYZ in the JavaScript ecosystem. #### Related Links List of links with more information about the topic to provide brackground or the information to be shared. #### Project contacts Add a list of GitHub handles for those within the project that have volunteered to be contacated when necessary by ambassadors to get more info about the message to be promoted. #### Node.js is a great choice for a JavaScript runtime ##### Goal Highlight the benefits of chosing Node.js as your backend JavaScript runtime. Focus on what is great about Node.js without drawing comparisons to alternatives. We don't want to say negative things about other options, only highlight what is great about Node.js as a choice. Some of the things to highlight include: * How widely it is used (you never get fired for chosing Node.js). * The openess of the project. It is part of the OpenJS Foundation and it's governance is set up to avoid any one company from dominating the project. Decisions are made by the collaborators (of which there are quite a few) versus a small number of people. * It has predictable and stable releases and has delivered on the release schedule since 2015. * It was a well defined security release process and manages security releases well. * As the defacto standard, it has the highest likelihood of being supported for a given package on npm. * It is not dependent on any one company for its continued existence reducing risk of using it. * The large number of platforms supported. * Asynchronous non-blocking i/o architecture drives high transactional throughput, making it ideal for web workloads. * Single threaded programming model enables very low resource consumption, making it ideal for containerised workloads. * Highly vibrant ecosystem with enterprise support from many vendors. #### Related Links * <https://github.com/nodejs/release> * <https://github.com/nodejs/node/blob/main/doc/contributing/security-release-process.md> * <https://github.com/nodejs/TSC/blob/main/TSC-Charter.md> * <https://github.com/mhdawson/presentations/blob/main/2024/NodeConfEU_2024-Node.js_whats_next.pdf> for slide usage and topping recent surveys. #### Project contacts * @mhdawson	7.26 KB	2025-02-28 19:16
📄 api-documentation.md # Node.js API Documentation Tooling The Node.js API documentation is generated by an in-house tooling that resides within the [tools/doc](https://github.com/nodejs/node/tree/main/tools/doc) directory. The build process (using `make doc` or `make doc-only`) uses this tooling to parse the markdown files in [`doc/api/`][] and generate the following: 1. Human-readable HTML in `out/doc/api/.html` 2. A JSON representation in `out/doc/api/.json` These artifacts are published to nodejs.org for multiple versions of Node.js. As an example the latest version of the human-readable HTML is published to [nodejs.org/en/doc](https://nodejs.org/en/docs/), and the latest version of the json documentation is published to [nodejs.org/api/all.json](https://nodejs.org/api/all.json) The artifacts are built as part of release builds by running the [doc-upload](https://github.com/nodejs/node/blob/1a83ad6a693f851199608ae957ac5d4f76871485/Makefile#L1218-L1224) Makefile target as part of the release-sources part of the iojs+release job. This target runs the `doc` target to build the docs and then uses `scp` to copy them onto the staging/www server into a directory of the form `/home/staging/nodejs/<type>/<full_version>/docs` where <type> is e.g. release, nightly, etc. The promotion step (either automatic for nightlies or manual for releases) then moves the docs to `/home/dist/nodejs/docs/\<full\_version>` where they are served by node.org. The key things to know about the tooling include: 1. The entry-point is `tools/doc/generate.js`. 2. The tooling supports the CLI arguments listed in the table below. 3. The tooling processes one file at a time. 4. The tooling uses a set of dependencies as described in the dependencies section. 5. The tooling parses the input files and does several transformations to the AST (Abstract Syntax Tree). 6. The tooling generates a JSON output that contains the metadata and content of the Markdown file. 7. The tooling generates a HTML output that contains a human-readable and ready to-view version of the file. This documentation serves the purpose of explaining the existing tooling processes, to allow easier maintenance and evolution of the tooling. It is not meant to be a guide on how to write documentation for Node.js. #### Vocabulary & Good to Know's * AST means "Abstract Syntax Tree" and it is a data structure that represents the structure of a certain data format. In our case, the AST is a "graph" representation of the contents of the Markdown file. * MDN means [Mozilla Developer Network](https://developer.mozilla.org/en-US/) and it is a website that contains documentation for web technologies. We use it as a reference for the structure of the documentation. * The [Stability Index](https://nodejs.org/dist/latest/docs/api/documentation.html#stability-index) is used to community the Stability of a given Node.js module. The Stability levels include: * Stability 0: Deprecated. (This module is Deprecated) * Stability 1: Experimental. (This module is Experimental) * Stability 2: Stable. (This module is Stable) * Stability 3: Legacy. (This module is Legacy) * Within Remark YAML snippets `<!-- something -->` are considered HTML nodes, that's because YAML isn't valid Markdown content. (Doesn't abide by the Markdown spec) * "New Tooling" references to the (written from-scratch) API build tooling introduced in `nodejs/nodejs.dev` that might replace the current one from `nodejs/node` ## CLI Arguments The tooling requires a `filename` argument and supports extra arguments (some also required) as shown below: \| Argument \| Description \| Required \| Example \| \| --------------------- \| -------------------------------------------------------------------------------------------------------------------------------------- \| -------- \| ---------------------------------- \| \| `--node-version=` \| The version of Node.js that is being documented. It defaults to `process.version` which is supplied by Node.js itself \| No \| v19.0.0 \| \| `--output-directory=` \| The directory where the output files will be generated. \| Yes \| `./out/api/` \| \| `--apilinks=` \| This file is used as an index to specify the source file for each module \| No \| `./out/doc/api/apilinks.json` \| \| `--versions-file=` \| This file is used to specify an index of all previous versions of Node.js. It is used for the Version Navigation on the API docs page. \| No \| `./out/previous-doc-versions.json` \| Note: both of the `apilinks` and `versions-file` parameters are generated by the Node.js build process (Makefile). And they're files containing a JSON object. ### Basic Usage ```bash # cd tools/doc npm run node-doc-generator ${filename} ``` OR ```bash # nodejs/node root directory make doc ``` ## Dependencies and how the Tooling works internally The API tooling uses an-AST-alike library called [unified](https://github.com/unifiedjs/unified) for processing the Input file as a Graph that supports easy modification and update of its nodes. In addition to `unified` we also use [Remark](https://github.com/remarkjs/remark) for manipulating the Markdown part, and [Rehype](https://github.com/rehypejs/rehype) to help convert to and from Markdown. ### What are the steps of the internal tooling? The tooling uses `unified` pipe-alike engine to pipe each part of the process. (The description below is a simplified version) * Starting from reading the Frontmatter section of the Markdown file with [remark-frontmatter](https://www.npmjs.com/package/remark-frontmatter). * Then the tooling goes to parse the Markdown by using `remark-parse` and adds support to [GitHub Flavoured Markdown](https://github.github.com/gfm/). * The tooling proceeds by parsing some of the Markdown nodes and transforming them to HTML. * The tooling proceeds to generate the JSON output of the file. * Finally it does its final node transformations and generates a stringified HTML. * It then stores the output to a JSON file and adds extra styling to the HTML and then stores the HTML file. ### What each file is responsible for? The files listed below are the ones referenced and actually used during the build process of the API docs as we see on <https://nodejs.org/api>. The remaining files from the directory might be used by other steps of the Node.js Makefile or might even be deprecated/remnant of old processes and might need to be revisited/removed. * `html.mjs`: Responsible for transforming nodes by decorating them with visual artifacts for the HTML pages; * For example, transforming man or JS doc references to links correctly referring to respective External documentation. * `json.mjs`: Responsible for generating the JSON output of the file; * It is mostly responsible for going through the whole Markdown file and generating a JSON object that represent the Metadata of a specific Module. * For example, for the FS module, it will generate an object with all its methods, events, classes and use several regular expressions (ReGeX) for extracting the information needed. * `generate.mjs`: Main entry-point of doc generation for a specific file. It does e2e processing of a documentation file; * `allhtml.mjs`: A script executed after all files are generated to create a single "all" page containing all the HTML documentation; * `alljson.mjs`: A script executed after all files are generated to create a single "all" page containing all the JSON entries; * `markdown.mjs`: Contains utility to replace Markdown links to work with the <https://nodejs.org/api/> website. * `common.mjs`: Contains a few utility functions that are used by the other files. * `type-parser.mjs`: Used to replace "type references" (e.g. "String", or "Buffer") to the correct Internal/External documentation pages (i.e. MDN or other Node.js documentation pages). Note: It is important to mention that other files not mentioned here might be used during the process but are not relevant to the generation of the API docs themselves. You will notice that a lot of the logic within the build process is specific to the current <https://nodejs.org/api/> infrastructure. Just as adding some JavaScript snippets, styles, transforming certain Markdown elements into HTML, and adding certain HTML classes or such things. Note: Regarding the previous Note it is important to mention that we're currently working on an API tooling that is generic and independent of the current Nodejs.org Infrastructure. [The new tooling that is functional is available at the nodejs.dev repository](https://github.com/nodejs/nodejs.dev/blob/main/scripts/syncApiDocs.js) and uses plain ReGeX (No AST) and [MDX](https://mdxjs.com/). ## The Build Process The build process that happens on `generate.mjs` follows the steps below: * Links within the Markdown are replaced directly within the source Markdown (AST) (`markdown.replaceLinks`) * This happens within `markdown.mjs` and basically it adds suffixes or modifies link references within the Markdown * This is necessary for the `https://nodejs.org` infrastructure as all pages are suffixed with `.html` * Text (and some YAML) Nodes are transformed/modified through `html.preprocessText` * JSON output is generated through `json.jsonAPI` * The title of the page is inferred through `html.firstHeader` * Nodes are transformed into HTML Elements through `html.preprocessElements` * The HTML Table of Contents (ToC) is generated through `html.buildToc` ### `html.mjs` This file is responsible for doing node AST transformations that either update Markdown nodes to decorate them with more data or transform them into HTML Nodes that attain a certain visual responsibility; For example, to generate the "Added at" label, or the Source Links or the Stability Index, or the History table. Note: Methods not listed below are either not relevant or utility methods for string/array/object manipulation (e.g.: are used by the other methods mentioned below). #### `preprocessText` New Tooling: Most of the features within this method are available within the new tooling. This method does two things: * Replaces the Source Link YAML entry `<-- source_link= -->` into a "Source Link" HTML anchor element. * Replaces type references within the Markdown (text) (i.e.: "String", "Buffer") into the correct HTML anchor element that links to the correct documentation page. * The original node then gets mutated from text to HTML. * It also updates references to Linux "MAN" pages to Web versions of them. #### `firstHeader` New Tooling: All features within this method are available within the new Tooling. Is used to attempt to extract the first heading of the page (recursively) to define the "title" of the page. Note: As all API Markdown files start with a Heading, this could possibly be improved to a reduced complexity. #### `preprocessElements` New Tooling: All features within this method are available within the new tooling. This method is responsible for doing multiple transformations within the AST Nodes, in majority, transforming the source node in respective HTML elements with diverse responsibilities, such as: * Updating Markdown `code` blocks by adding Language highlighting * It also adds the "CJS"/"MJS" switch to Nodes that are followed by their CJS/ESM equivalents. * Increasing the Heading level of each Heading * Parses YAML blocks and transforms them into HTML elements (See more at the `parseYAML` method) * Updates BlockQuotes that are prefixed by the "Stability" word into a Stability Index HTML element. #### `parseYAML` New Tooling: Most of the features within this method are available within the new tooling. This method is responsible for parsing the `<--YAML snippets -->` and transforming them into HTML elements. It follows a certain kind of "schema" that basically constitutes in the following options: \| YAML Key \| Description \| Example \| Example Result \| Available on new tooling \| \| ------------- \| ------------------------------------------------------------------------------------------------------------------------------- \| ----------------------------------------------------- \| --------------------------- \| ------------------------ \| \| `added` \| It's used to reference when a certain "module", "class" or "method" was added on Node.js \| `added: v0.1.90` \| `Added in: v0.1.90` \| Yes \| \| `deprecated` \| It's used to reference when a certain "module", "class" or "method" was deprecated on Node.js \| `deprecated: v0.1.90` \| `Deprecated since: v0.1.90` \| Yes \| \| `removed` \| It's used to reference when a certain "module", "class" or "method" was removed on Node.js \| `removed: v0.1.90` \| `Removed in: v0.1.90` \| No \| \| `changes` \| It's used to describe all the changes (historical ones) that happened within a certain "module", "class" or "method" in Node.js \| `[{ version: v0.1.90, pr-url: '', description: '' }]` \| -- \| Yes \| \| `napiVersion` \| It's used to describe in which version of the N-API this "module", "class" or "method" is available within Node.js \| `napiVersion: 1` \| `N-API version: 1` \| Yes \| Note: The `changes` field gets prepended with the `added`, `deprecated` and `removed` fields if they exist. The table only gets generated if a `changes` field exists. In the new tooling only "added" is prepended for now. #### `buildToc` New Tooling: This feature is natively available within the new tooling through MDX. This method generates the Table of Contents based on all the Headings of the Markdown file. #### `altDocs` New Tooling: All features within this method are available within the new tooling. This method generates a version picker for the current page to be shown in older versions of the API docs. ### `json.mjs` This file is responsible for generating a JSON object that (supposedly) is used for IDE-Intellisense or for indexing of all the "methods", "classes", "modules", "events", "constants" and "globals" available within a certain Markdown file. It attempts a best effort extraction of the data by using several regular expression patterns (ReGeX). Note: JSON output generation is currently not supported by the new tooling, but it is in the pipeline for development. #### `jsonAPI` This method traverses all the AST Nodes by iterating through each one of them and infers the kind of information each node contains through ReGeX. Then it mutate the data and appends it to the final JSON object. For a more in-depth information we recommend to refer to the `json.mjs` file as it contains a lot of comments. [`doc/api/`]: https://github.com/nodejs/node/tree/main/doc/api	15.4 KB	2025-02-28 19:16
📄 backporting-to-release-lines.md # How to backport a pull request to a release line ## Staging branches Each release line has a staging branch that serves as a workspace for preparing releases. The branch format is `vN.x-staging`, where `N` is the major release number. For active staging branches, refer to the [Release Schedule][]. ## Identifying changes that require a backport If a cherry-pick from `main` doesn't apply cleanly on a staging branch, the pull request will be labeled for the release line (e.g., `backport-requested-vN.x`). This indicates that manual backporting is required. ## Criteria for backporting The "Current" release line is more flexible than LTS lines. LTS branches, detailed in the [Release Plan][], require commits to mature in the Current release for at least two weeks before backporting. ## Labeling backport issues and PRs Use the following labels, with `N` in `vN.x` denoting the major release number: \| Label \| Description \| \| ----------------------- \| ------------------------------------------------------------------- \| \| backport-blocked-vN.x \| PRs for `vN.x-staging` blocked by pending backports from other PRs. \| \| backport-open-vN.x \| Indicates an open backport for the PR. \| \| backport-requested-vN.x \| PR awaiting manual backport to `vN.x-staging`. \| \| backported-to-vN.x \| PR successfully backported to `vN.x-staging`. \| \| baking-for-lts \| PRs awaiting LTS release after maturation in Current. \| \| lts-watch-vN.x \| PRs possibly included in `vN.x` LTS releases. \| \| vN.x \| Issues or PRs impacting `vN.x-staging` (or reproducible on vN.x). \| ## Submitting a backport pull request For the following steps, let's assume that you need to backport PR `123` to the vN.x release line. All commands will use the `vN.x-staging` branch as the target branch. In order to submit a backport pull request to another branch, simply replace `N` with the version number for the targeted release line. ### Automated process 1. Ensure [`@node-core/utils`][] is installed. 2. Execute [`git node backport`][] command: ```bash # Example: Backport PR 123 to vN.x-staging git node backport 123 --to=N ``` 3. Proceed to step 5 in the Manual section below. ### Manual process 1. Checkout the `vN.x-staging` branch. 2. Verify that the local staging branch is up to date with the remote. 3. Create a new branch based on `vN.x-staging`: ```bash git fetch upstream vN.x-staging:vN.x-staging -f git checkout -b backport-123-to-vN.x vN.x-staging ``` 4. Cherry-pick the desired commit(s): ```bash git cherry-pick <commit hash> ``` 5. Resolve conflicts using `git add` and `git cherry-pick --continue`. 6. Leave the commit message as is. If you think it should be modified, comment in the pull request. The `Backport-PR-URL` metadata does need to be added to the commit, but this will be done later. 7. Verify that `make -j4 test` passes. 8. Push the changes to your fork. 9. Open a pull request: * Target `vN.x-staging`. * Title format: `[vN.x backport] <commit title>` (e.g., `[v20.x backport] process: improve performance of nextTick`). * Reference the original PR in the description. 10. Update the `backport-requested-vN.x` label on the original pull request to `backport-open-vN.x`. 11. If conflicts arise during the review process, the following command be used to rebase: ```bash git pull --rebase upstream vN.x-staging ``` Once merged, update the original PR's label from `backport-open-vN.x` to `backported-to-vN.x`. [Release Plan]: https://github.com/nodejs/Release#release-plan [Release Schedule]: https://github.com/nodejs/Release#release-schedule [`@node-core/utils`]: https://github.com/nodejs/node-core-utils [`git node backport`]: https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-backport	3.95 KB	2025-02-28 19:16
📄 building-node-with-ninja.md # Building Node.js with Ninja The purpose of this guide is to show how to build Node.js using [Ninja][], as doing so can be significantly quicker than using `make`. Please see [Ninja's site][Ninja] for installation instructions (Unix only). [Ninja][] is supported in the Makefile. Run `./configure --ninja` to configure the project to run the regular `make` commands with Ninja. When modifying only the JS layer in `lib`, you can use: ```bash ./configure --ninja --node-builtin-modules-path "$(pwd)" ``` For example, `make` will execute `ninja -C out/Release` internally to produce a compiled release binary, It will also execute `ln -fs out/Release/node node`, so that you can execute `./node` at the project's root. When running `make`, you will see output similar to the following if the build has succeeded: ```console ninja: Entering directory `out/Release` [4/4] LINK node, POSTBUILDS ``` The bottom line will change while building, showing the progress as `[finished/total]` build steps. This is useful output that `make` does not produce and is one of the benefits of using Ninja. When using Ninja, builds are always run in parallel, based by default on the number of CPUs your system has. You can use the `-j` parameter to override this behavior, which is equivalent to the `-j` parameter in the regular `make`: ```bash make -j4 # With this flag, Ninja will limit itself to 4 parallel jobs, # regardless of the number of cores on the current machine. ``` Note: if you are on macOS and use GNU Make version `3.x`, the `-jn` flag will not work. You can either upgrade to `v4.x` (e.g. using a package manager such as [Homebrew](https://formulae.brew.sh/formula/make#default)) or use `make JOBS=n`. ## Producing a debug build To create a debug build rather than a release build: ```bash ./configure --ninja --debug && make ``` ## Customizing `ninja` path On some systems (such as RHEL7 and below), the Ninja binary might be installed with a different name. For these systems use the `NINJA` env var: ```bash ./configure --ninja && NINJA="ninja-build" make ``` [Ninja]: https://ninja-build.org/	2.08 KB	2025-02-28 19:16
📄 code-of-conduct.md # Code of Conduct The Node.js project has a [Code of Conduct][] that _all_ contributors are expected to follow. This code describes the _minimum_ behavior expectations for all contributors. As a contributor to Node.js, how you choose to act and interact towards your fellow contributors, as well as to the community, will reflect back not only on yourself but on the project as a whole. The Code of Conduct is designed and intended, above all else, to help establish a culture within the project that allows anyone and everyone who wants to contribute to feel safe doing so. Should any individual act in any way that is considered in violation of the [Code of Conduct][], corrective actions will be taken. It is possible, however, for any individual to _act_ in such a manner that is not in violation of the strict letter of the Code of Conduct guidelines while still going completely against the spirit of what that Code is intended to accomplish. Open, diverse, and inclusive communities live and die on the basis of trust. Contributors can disagree with one another so long as they trust that those disagreements are in good faith and everyone is working towards a common goal. ## Bad actors All contributors to Node.js tacitly agree to abide by both the letter and spirit of the [Code of Conduct][]. Failure, or unwillingness, to do so will result in contributions being respectfully declined. A _bad actor_ is someone who repeatedly violates the spirit of the Code of Conduct through failure to regulate how they interact with others. In doing so, bad actors alienate other contributors, discourage collaboration, and generally reflect poorly on the project as a whole. Being a bad actor may be intentional or unintentional. Typically, unintentional bad behavior can be easily corrected by being quick to apologize and correct course _even if you are not entirely convinced you need to_. Giving other contributors the benefit of the doubt and having a sincere willingness to admit that you _might_ be wrong is critical for any successful open collaboration. Don't be a bad actor. [Code of Conduct]: https://github.com/nodejs/admin/blob/HEAD/CODE_OF_CONDUCT.md	2.12 KB	2025-02-28 19:16
📄 collaborator-guide.md # Node.js collaborator guide ## Contents * [Issues and pull requests](#issues-and-pull-requests) * [Welcoming first-time contributors](#welcoming-first-time-contributors) * [Closing issues and pull requests](#closing-issues-and-pull-requests) * [Author ready pull requests](#author-ready-pull-requests) * [Handling own pull requests](#handling-own-pull-requests) * [Security issues](#managing-security-issues) * [Accepting modifications](#accepting-modifications) * [Code reviews](#code-reviews) * [Consensus seeking](#consensus-seeking) * [Waiting for approvals](#waiting-for-approvals) * [Testing and CI](#testing-and-ci) * [Useful Jenkins CI jobs](#useful-jenkins-ci-jobs) * [Starting a Jenkins CI job](#starting-a-jenkins-ci-job) * [Internal vs. public API](#internal-vs-public-api) * [Breaking changes](#breaking-changes) * [Breaking changes and deprecations](#breaking-changes-and-deprecations) * [Breaking changes to internal elements](#breaking-changes-to-internal-elements) * [Unintended breaking changes](#unintended-breaking-changes) * [Reverting commits](#reverting-commits) * [Introducing new modules](#introducing-new-modules) * [Additions to Node-API](#additions-to-node-api) * [Deprecations](#deprecations) * [Involving the TSC](#involving-the-tsc) * [Landing pull requests](#landing-pull-requests) * [Using the commit queue GitHub labels](#using-the-commit-queue-github-labels) * [Using `git-node`](#using-git-node) * [Technical HOWTO](#technical-howto) * [Troubleshooting](#troubleshooting) * [I made a mistake](#i-made-a-mistake) * [Long Term Support](#long-term-support) * [What is LTS?](#what-is-lts) * [How are LTS branches managed?](#how-are-lts-branches-managed) * [How can I help?](#how-can-i-help) * [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker) This document explains how collaborators manage the Node.js project. Collaborators should understand the [guidelines for new contributors](../../CONTRIBUTING.md) and the [project governance model](../../GOVERNANCE.md). ## Issues and pull requests Mind these guidelines, the opinions of other collaborators, and guidance of the [TSC][]. Notify other qualified parties for more input on an issue or a pull request. See [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker). ### Welcoming first-time contributors Always show courtesy to individuals submitting issues and pull requests. Be welcoming to first-time contributors, identified by the GitHub First-time contributor badge. For first-time contributors, check if the commit author is the same as the pull request author. This way, once their pull request lands, GitHub will show them as a _Contributor_. Ask if they have configured their git [username][git-username] and [email][git-email] to their liking. ### Closing issues and pull requests Collaborators can close any issue or pull request that is not relevant to the future of the Node.js project. Where this is unclear, leave the issue or pull request open for several days to allow for discussion. Where this does not yield evidence that the issue or pull request has relevance, close it. Remember that issues and pull requests can always be re-opened if necessary. ### Author ready pull requests A pull request is _author ready_ when: * There is a CI run in progress or completed. * There is at least one collaborator approval. * There are no outstanding review comments. Please always add the `author ready` label to the pull request in that case. Please always remove it again as soon as the conditions are not met anymore. ### Handling own pull requests When you open a pull request, [start a CI](#testing-and-ci) right away. Later, after new code changes or rebasing, start a new CI. As soon as the pull request is ready to land, please do so. This allows other collaborators to focus on other pull requests. If your pull request is not ready to land but is [author ready](#author-ready-pull-requests), add the `author ready` label. If you wish to land the pull request yourself, use the "assign yourself" link to self-assign it. ### Managing security issues Use the process outlined in [SECURITY.md][] to report security issues. If a user opens a security issue in the public repository: * Ask the user to submit a report through HackerOne as outlined in [SECURITY.md][]. * Move the issue to the private repository called [premature-disclosures](https://github.com/nodejs/premature-disclosures). * For any related pull requests, create an associated issue in the `premature-disclosures` repository. Add a copy of the patch for the pull request to the issue. Add screenshots of discussion from the pull request to the issue. * [Open a ticket with GitHub](https://support.github.com/contact) to delete the pull request using Node.js (team) as the account organization. * Open a new issue in the public repository with the title `FYI - pull request deleted #YYYY`. Include an explanation for the user: > FYI @xxxx we asked GitHub to delete your pull request while we work on > releases in private. * Email `tsc@iojs.org` with links to the issues in the `premature-disclosures` repository. ## Accepting modifications Contributors propose modifications to Node.js using GitHub pull requests. This includes modifications proposed by TSC members and other collaborators. A pull request must pass code review and CI before landing into the codebase. ### Code reviews At least two collaborators must approve a pull request before the pull request lands. One collaborator approval is enough if the pull request has been open for more than seven days. Approving a pull request indicates that the collaborator accepts responsibility for the change. Approval must be from collaborators who are not authors of the change. Ideally pull requests for dependencies should be generated by automation. Pay special attention to pull requests for dependencies which have not been automatically generated and follow the guidance in [Maintaining Dependencies](https://github.com/nodejs/node/blob/main/doc/contributing/maintaining/maintaining-dependencies.md#updating-dependencies). In some cases, it might be necessary to summon a GitHub team to a pull request for review by @-mention. See [Who to CC in the issue tracker](#who-to-cc-in-the-issue-tracker). If you are the first collaborator to approve a pull request that has no CI yet, please [start one](#testing-and-ci). Please also start a new CI if the pull request creator pushed new code since the last CI run. ### Consensus seeking A pull request can land if it has the needed [approvals](#code-reviews), [CI](#testing-and-ci), [wait time](#waiting-for-approvals) and no [outstanding objections](#objections). [Breaking changes](#breaking-changes) must receive [TSC review](#involving-the-tsc) in addition to other requirements. If a pull request meets all requirements except the [wait time](#waiting-for-approvals), please add the [`author ready`](#author-ready-pull-requests) label. #### Objections Collaborators can object to a pull request by using the "Request Changes" GitHub feature. Dissent comments alone don't constitute an objection. Any pull request objection must include a clear reason for that objection, and the objector must remain responsive for further discussion towards consensus about the direction of the pull request. Where possible, provide a set of actionable steps alongside the objection. If the objection is not clear to others, another collaborator can ask an objecting collaborator to explain their objection or to provide actionable steps to resolve the objection. If the objector is unresponsive for seven days after a collaborator asks for clarification, a collaborator may dismiss the objection. Pull requests with outstanding objections must remain open until all objections are satisfied. If reaching consensus is not possible, a collaborator can escalate the issue to the TSC by pinging `@nodejs/tsc` and adding the `tsc-agenda` label to the issue. #### Helpful resources * [How to Do Code Reviews Like a Human (Part One)](https://mtlynch.io/human-code-reviews-1/) * [How to Do Code Reviews Like a Human (Part Two)](https://mtlynch.io/human-code-reviews-2/) * [Code Review Etiquette](https://css-tricks.com/code-review-etiquette/) ### Waiting for approvals Before landing pull requests, allow 48 hours for input from other collaborators. Certain types of pull requests can be fast-tracked and can land after a shorter delay. For example: * Focused changes that affect only documentation and/or the test suite: * `code-and-learn` tasks often fall into this category. * `good-first-issue` pull requests might also be suitable. * Changes that fix regressions: * Regressions that break the workflow (red CI or broken compilation). * Regressions that happen right before a release, or reported soon after. To propose fast-tracking a pull request, apply the `fast-track` label. Then a GitHub Actions workflow will add a comment that collaborators can upvote. If someone disagrees with the fast-tracking request, remove the label. Do not fast-track the pull request in that case. The pull request can be fast-tracked if two collaborators approve the fast-tracking request. To land, the pull request itself still needs two collaborator approvals and a passing CI. Collaborators can request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt. ### Testing and CI All fixes must have a test case which demonstrates the defect. The test should fail before the change, and pass after the change. Do not land any pull requests without the necessary passing CI runs. A passing (green) GitHub Actions CI result is required. A passing (green or yellow) [Jenkins CI](https://ci.nodejs.org/) is also required if the pull request contains changes that will affect the `node` binary. This is because GitHub Actions CI does not cover all the environments supported by Node.js. <details> <summary>Changes that affect the `node` binary</summary> Changes in the following folders (except comment-only changes) are guaranteed to affect the `node` binary: * `deps/` * `lib/` * `src/` * `test/` * `tools/code_cache/` * `tools/gyp/` * `tools/icu/` * `tools/inspector-protocol/` * `tools/msvs/` * `tools/snapshot/` * `tools/v8_gypfiles/` There are some other files that touch the build chain. Changes in the following files also qualify as affecting the `node` binary: * `tools/.py` `.gyp` `.gypi` `configure` * `configure.py` * `Makefile` * `vcbuild.bat` </details> If there are GitHub Actions CI failures unrelated to the change in the pull request, try the "🔄 Re-run all jobs" button, on the right-hand side of the "Checks" tab. If there are Jenkins CI failures unrelated to the change in the pull request, try "Resume Build". It is in the left navigation of the relevant `node-test-pull-request` job. It will preserve all the green results from the current job but re-run everything else. Start a fresh CI if more than seven days have elapsed since the original failing CI as the compiled binaries for the Windows and ARM platforms are only kept for seven days. If new commits are pushed to the pull request branch after the latest Jenkins CI run, a fresh CI run is required. It can be started by pressing "Retry" on the left sidebar, or by adding the `request-ci` label to the pull request. #### Useful Jenkins CI jobs * [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) is the CI job to test pull requests. It runs the `build-ci` and `test-ci` targets on all supported platforms. * [`citgm-smoker`](https://ci.nodejs.org/job/citgm-smoker/) uses [`CitGM`](https://github.com/nodejs/citgm) to allow you to run `npm install && npm test` on a large selection of common modules. This is useful to check whether a change will cause breakage in the ecosystem. * [`node-stress-single-test`](https://ci.nodejs.org/job/node-stress-single-test/) can run a group of tests over and over on a specific platform. Use it to check that the tests are reliable. * [`node-test-commit-v8-linux`](https://ci.nodejs.org/job/node-test-commit-v8-linux/) runs the standard V8 tests. Run it when updating V8 in Node.js or floating new patches on V8. * [`node-test-commit-custom-suites-freestyle`](https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/) enables customization of test suites and parameters. It can execute test suites not used in other CI test runs (such as tests in the `internet` or `pummel` directories). It can also make sure tests pass when provided with a flag not used in other CI test runs (such as `--worker`). #### Starting a Jenkins CI job From the CI Job page, click "Build with Parameters" on the left side. You generally need to enter only one or both of the following options in the form: * `GIT_REMOTE_REF`: Change to the remote portion of git refspec. To specify the branch this way, `refs/heads/BRANCH` is used (e.g. for `main` -> `refs/heads/main`). For pull requests, it will look like `refs/pull/PR_NUMBER/head` (e.g. for pull request #42 -> `refs/pull/42/head`). * `REBASE_ONTO`: Change that to `origin/main` so the pull request gets rebased onto `main`. This can especially be important for pull requests that have been open a while. Look at the list of jobs on the left hand side under "Build History" and copy the link to the one you started (which will be the one on top, but click through to make sure it says something like "Started 5 seconds ago" (top right) and "Started by user ...". Copy/paste the URL for the job into a comment in the pull request. [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) is an exception where the GitHub bot will automatically post for you. The [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) CI job can be started by adding the `request-ci` label into the pull request. Once this label is added, `github-actions bot` will start the `node-test-pull-request` automatically. If the `github-actions bot` is unable to start the job, it will update the label with `request-ci-failed`. ### Internal vs. public API All functionality in the official Node.js documentation is part of the public API. Any undocumented object, property, method, argument, behavior, or event is internal. There are exceptions to this rule. Node.js users have come to rely on some undocumented behaviors. Collaborators treat many of those undocumented behaviors as public. All undocumented functionality exposed via `process.binding(...)` is internal. All undocumented functionality in `lib/internal/*/.js` is internal. It is public, though, if it is re-exported by code in `lib/.js`. Non-exported `Symbol` properties and methods are internal. Any undocumented object property or method that begins with `_` is internal. Any native C/C++ APIs/ABIs requiring the `NODE_WANT_INTERNALS` flag are internal. Sometimes, there is disagreement about whether functionality is internal or public. In those cases, the TSC makes a determination. For undocumented APIs that are public, open a pull request documenting the API. ### Breaking changes At least two TSC voting members must approve backward-incompatible changes to the `main` branch. Examples of breaking changes include: Removal or redefinition of existing API arguments. * Changing return values. * Removing or modifying existing properties on an options argument. * Adding or removing errors. * Altering expected timing of an event. * Changing the side effects of using a particular API. #### Breaking changes and deprecations Existing stable public APIs that change in a backward-incompatible way must undergo deprecation. The exceptions to this rule are: * Adding or removing errors thrown or reported by a public API. * Emitting a runtime warning. * Changing error messages for errors without error code. * Altering the timing and non-internal side effects of the public API. * Changes to errors thrown by dependencies of Node.js, such as V8. * One-time exceptions granted by the TSC. For more information, see [Deprecations](#deprecations). #### Breaking changes to internal elements Breaking changes to internal elements can occur in semver-patch or semver-minor commits. Take significant care when making and reviewing such changes. Make an effort to determine the potential impact of the change in the ecosystem. Use [Canary in the Goldmine](https://github.com/nodejs/citgm) to test such changes. If a change will cause ecosystem breakage, then it is semver-major. Consider providing a Public API in such cases. #### Unintended breaking changes Sometimes, a change intended to be non-breaking turns out to be a breaking change. If such a change lands on the `main` branch, a collaborator can revert it. As an alternative to reverting, the TSC can apply the semver-major label after-the-fact. If the change has already been backported to release lines open an issue in the TSC repository to discuss how best to proceed. In the past we have often reverted in the release lines and kept the change on main. The decision to revert or not most often is based on limiting the impact to the ecosystem and how quickly the breaking change is discovered. If the change is reverted make sure to: * consider if additional tests can be added to avoid a similar breaking change being missed in the future. * consider if adding packages to CITGM would have helped catch the breaking change. * ensure the changelog with the revert clearly explains the situation and it's impact on those who may have already used the updated API. In either case make sure that the documentation and changelog for the original breaking change are updated to reflect the breaking behavior. ##### Reverting commits Revert commits with `git revert <HASH>` or `git revert <FROM>..<TO>`. The generated commit message will not have a subsystem and might violate line length rules. That is OK. Append the reason for the revert and any `Refs` or `Fixes` metadata. Raise a pull request like any other change. ### Introducing new modules Treat commits that introduce new core modules with extra care. New modules must only be added with the `node:` prefix. When adding promises to an existing API, add `/promises` (`inspector/promises`, etc.). Apply the `semver-major` label to the addition. If the new module name is free in npm, register a placeholder in the module registry as soon as possible. Link to the pull request that introduces the new core module in the placeholder's `README`. If the module name is not free and the module is not widely used, contact the owner to see if they would be willing to transfer it to the project. We register a placeholder without the `node:` prefix whenever possible to avoid confusion and typosquatting attacks. For pull requests introducing new core modules: * Allow at least one week for review. * Land only after sign-off from at least two TSC voting members. * Land with a [Stability Index][] of Experimental. The module must remain Experimental until a semver-major release. ### Introducing new APIs on the global scope Exposing new APIs to the global scope that are available without an `import` or `require` call, including introducing new interfaces on `globalThis` like `globalThis.navigator`, and adding new properties on interfaces on `globalThis` like well known symbols, could break feature detection and Node.js environment detection. Exposing new APIs to the global scope unconditionally without any CLI flags must always be labeled as `semver-major`. The `semver-major` label may be waived through the regular TSC consensus process. It is recommended to start with exposing APIs to the global scope with an experimental CLI flag `--experimental-<feature-name>`, without being labeled as `semver-major`. When the new APIs are feature complete, turn the flag on by default with a CLI flag `--no-experimental-<feature-name>` to opt-out. ### Additions to Node-API Node-API provides an ABI-stable API guaranteed for future Node.js versions. Node-API additions call for unusual care and scrutiny. If a change adds to `node_api.h`, `js_native_api.h`, `node_api_types.h`, or `js_native_api_types.h`, consult [the relevant guide](https://github.com/nodejs/node/blob/HEAD/doc/contributing/adding-new-napi-api.md). ### Deprecations Node.js uses three [Deprecation][] levels. For all deprecated APIs, the API documentation must state the deprecation status. * Documentation-Only Deprecation * A deprecation notice appears in the API documentation. * There are no functional changes. * By default, there will be no warnings emitted for such deprecations at runtime. * Might cause a runtime warning with the [`--pending-deprecation`][] flag or `NODE_PENDING_DEPRECATION` environment variable. * Runtime Deprecation * Emits a warning at runtime on first use of the deprecated API. * If used with the [`--throw-deprecation`][] flag, will throw a runtime error. * End-of-Life * The API is no longer subject to the semantic versioning rules. * Backward-incompatible changes including complete removal of such APIs can occur at any time. Apply the `notable-change` label to all pull requests that introduce Documentation-Only Deprecations. Such deprecations have no impact on code execution. Thus, they are not breaking changes (`semver-major`). Runtime Deprecations and End-of-Life APIs (internal or public) are breaking changes (`semver-major`). The TSC can make exceptions, deciding that one of these deprecations is not a breaking change. Avoid Runtime Deprecations when an alias or a stub/no-op will suffice. An alias or stub will have lower maintenance costs for end users and Node.js core. All deprecations receive a unique and immutable identifier. Documentation, warnings, and errors use the identifier when referring to the deprecation. The documentation for the deprecation identifier must always remain in the API documentation. This is true even if the deprecation is no longer in use (for example, due to removal of an End-of-Life deprecated API). <a id="deprecation-cycle"></a> A _deprecation cycle_ is a major release during which an API has been in one of the three Deprecation levels. Documentation-Only Deprecations can land in a minor release. They can not change to a Runtime Deprecation until the next major release. No API can change to End-of-Life without going through a Runtime Deprecation cycle. There is no rule that deprecated code must progress to End-of-Life. Documentation-Only and Runtime Deprecations can remain in place for an unlimited duration. Communicate pending deprecations and associated mitigations with the ecosystem as soon as possible. If possible, do it before the pull request adding the deprecation lands on the `main` branch. Use the `notable-change` label on pull requests that add or change the deprecation level of an API. ### Involving the TSC Collaborators can opt to elevate pull requests or issues to the [TSC][]. Do this if a pull request or issue: * Is labeled `semver-major`, or * Has a significant impact on the codebase, or * Is controversial, or * Is at an impasse among collaborators who are participating in the discussion. @-mention the `@nodejs/tsc` GitHub team if you want to elevate an issue to the [TSC][]. Do not use the GitHub UI on the right-hand side to assign to `@nodejs/tsc` or request a review from `@nodejs/tsc`. The TSC serves as the final arbiter where required. ## Landing pull requests 1. Avoid landing pull requests that have someone else as an assignee. Authors who wish to land their own pull requests will self-assign them. Sometimes, an author will delegate to someone else. If in doubt, ask the assignee whether it is okay to land. 2. Never use GitHub's green ["Merge pull request"][] button. Reasons for not using the web interface button: * The "Create a merge commit" method will add an unnecessary merge commit. * The "Squash and merge" method will add metadata (the pull request #) to the commit title. If more than one author contributes to the pull request, squashing only keeps one author. * The "Rebase and merge" method has no way of adding metadata to the commit. 3. Make sure CI is complete and green. If the CI is not green, check for unreliable tests and infrastructure failures. If there are no corresponding issues in the [node][unreliable tests] or [build](https://github.com/nodejs/build/issues) repositories, open new issues. Run a new CI any time someone pushes new code to the pull request. 4. Check that the commit message adheres to [commit message guidelines][]. 5. Add all necessary [metadata][git-node-metadata] to commit messages before landing. If you are unsure exactly how to format the commit messages, use the commit log as a reference. See [this commit][commit-example] as an example. For pull requests from first-time contributors, be [welcoming](#welcoming-first-time-contributors). Also, verify that their git settings are to their liking. If a pull request contains more than one commit, it can be landed either by squashing into one commit or by rebasing all the commits, or a mix of the two. Generally, a collaborator should land a pull request by squashing. If a pull request has more than one self-contained subsystem commits, a collaborator may land it as several commits. All commits should be self-contained, meaning every commit should pass all tests. This makes it much easier when bisecting to find a breaking change. ### Using the commit queue GitHub labels See the [commit queue guide][commit-queue.md]. ### Using `git-node` In most cases, using [the `git-node` command][git-node] of [`@node-core/utils`][] is enough to land a pull request. If you discover a problem when using this tool, please file an issue [to the issue tracker][node-core-utils-issues]. Quick example: ```bash npm install -g @node-core/utils git node land $PRID ``` To use `@node-core/utils`, you will need a GitHub access token. If you do not have one, `@node-core/utils` will create one for you the first time you use it. To do this, it will ask for your GitHub password and two-factor authentication code. If you wish to create the token yourself in advance, see [the `@node-core/utils` guide][node-core-utils-credentials]. ### Technical HOWTO Infrequently, it is necessary to manually perform the steps required to land a pull request rather than rely on `git-node`. <details> <Summary>Manual Landing Steps</Summary> Clear any `am`/`rebase` that might already be underway: ```bash git am --abort git rebase --abort ``` Checkout proper target branch: ```bash git checkout main ``` Update the tree (assumes your repository is set up as detailed in [CONTRIBUTING.md](./pull-requests.md#step-1-fork)): ```bash git fetch upstream git merge --ff-only upstream/main ``` Apply external patches: ```bash curl -L https://github.com/nodejs/node/pull/xxx.patch \| git am --whitespace=fix ``` If the merge fails even though recent CI runs were successful, try a 3-way merge: ```bash git am --abort curl -L https://github.com/nodejs/node/pull/xxx.patch \| git am -3 --whitespace=fix ``` If the 3-way merge succeeds, check the results against the original pull request. Build and test on at least one platform before landing. If the 3-way merge fails, then it is most likely that a conflicting pull request has landed since the CI run. You will have to ask the author to rebase. Check and re-review the changes: ```bash git diff upstream/main ``` Check the number of commits and commit messages: ```bash git log upstream/main...main ``` Squash commits and add metadata: ```bash git rebase -i upstream/main ``` This will open a screen like this (in the default shell editor): ```text pick 6928fc1 crypto: add feature A pick 8120c4c add test for feature A pick 51759dc crypto: feature B pick 7d6f433 test for feature B # Rebase f9456a2..7d6f433 onto f9456a2 # # Commands: # p, pick = use commit # r, reword = use commit, but edit the commit message # e, edit = use commit, but stop for amending # s, squash = use commit, but meld into previous commit # f, fixup = like "squash", but discard this commit's log message # x, exec = run command (the rest of the line) using shell # # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST. # # However, if you remove everything, the rebase will be aborted. # # Note that empty commits are commented out ``` Replace a couple of `pick`s with `fixup` to squash them into a previous commit: ```text pick 6928fc1 crypto: add feature A fixup 8120c4c add test for feature A pick 51759dc crypto: feature B fixup 7d6f433 test for feature B ``` Replace `pick` with `reword` to change the commit message: ```text reword 6928fc1 crypto: add feature A fixup 8120c4c add test for feature A reword 51759dc crypto: feature B fixup 7d6f433 test for feature B ``` Save the file and close the editor. When prompted, enter a new commit message for that commit. This is an opportunity to fix commit messages. * The commit message text must conform to the [commit message guidelines][]. * <a name="metadata"></a>Change the original commit message to include metadata. (The [`git node metadata`][git-node-metadata] command can generate the metadata for you). * Required: A `PR-URL:` line that references the full GitHub URL of the pull request. This makes it easy to trace a commit back to the conversation that led up to that change. * Optional: A `Fixes: X` line, where _X_ is the full GitHub URL for an issue. A commit message can include more than one `Fixes:` lines. * Optional: One or more `Refs:` lines referencing a URL for any relevant background. * Required: A `Reviewed-By: Name <email>` line for each collaborator who reviewed the change. * Useful for @mentions / contact list if something goes wrong in the pull request. * Protects against the assumption that GitHub will be around forever. Other changes might have landed on `main` since the successful CI run. As a precaution, run tests (`make -j4 test` or `vcbuild test`). Confirm that the commit message format is correct using [core-validate-commit](https://github.com/nodejs/core-validate-commit). ```bash git rev-list upstream/main...HEAD \| xargs core-validate-commit ``` Optional: For your own commits, force push the amended commit to the pull request branch. If your branch name is `bugfix`, then: `git push --force-with-lease origin main:bugfix`. Don't close the pull request. It will close after you push it upstream. It will have the purple merged status rather than the red closed status. If you close the pull request before GitHub adjusts its status, it will show up as a 0 commit pull request with no changed files. The order of operations is important. If you push upstream before you push to your branch, GitHub will close the issue with the red closed status. Time to push it: ```bash git push upstream main ``` Close the pull request with a "Landed in `<commit hash>`" comment. Even if your pull request shows the purple merged status, add the "Landed in \<commit hash>..\<commit hash>" comment if you added more than one commit. </details> ### Troubleshooting Sometimes, when running `git push upstream main`, you might get an error message like this: ```console To https://github.com/nodejs/node ! [rejected] main -> main (fetch first) error: failed to push some refs to 'https://github.com/nodejs/node' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. ``` That means a commit has landed since your last rebase against `upstream/main`. To fix this, pull with rebase from upstream, run the tests again, and (if the tests pass) push again: ```bash git pull upstream main --rebase make -j4 test git push upstream main ``` ### I made a mistake * Ping a TSC voting member. * With `git`, there's a way to override remote trees by force pushing (`git push -f`). This is generally forbidden as it creates conflicts in other people's forks. It is permissible for simpler slip-ups such as typos in commit messages. You are only allowed to force push to any Node.js branch within 10 minutes from your original push. If someone else pushes to the branch or the 10-minute period passes, consider the commit final. * Use `--force-with-lease` to reduce the chance of overwriting someone else's change. ### Long Term Support #### What is LTS? Long Term Support (LTS) guarantees 30-month support cycles for specific Node.js versions. You can find more information [in the full release plan](https://github.com/nodejs/Release#release-plan). Once a branch enters LTS, the release plan limits the types of changes permitted in the branch. #### How are LTS branches managed? Each LTS release has a corresponding branch (v10.x, v8.x, etc.). Each also has a corresponding staging branch (v10.x-staging, v8.x-staging, etc.). Commits that land on `main` are cherry-picked to each staging branch as appropriate. If a change applies only to the LTS branch, open the pull request against the _staging_ branch. Commits from the staging branch land on the LTS branch only when a release is being prepared. They might land on the LTS branch in a different order than they do in staging. Only members of @nodejs/backporters should land commits onto LTS staging branches. #### How can I help? When you send your pull request, please state if your change is breaking. Also state if you think your patch is a good candidate for backporting. For more information on backporting, please see the [backporting guide][]. There are several LTS-related labels: * `lts-watch-` labels are for pull requests to consider for landing in staging branches. For example, `lts-watch-v10.x` would be for a change to consider for the `v10.x-staging` branch. * `land-on-` are for pull requests that should land in a future v\.x release. For example, `land-on-v10.x` would be for a change to land in Node.js 10.x. Any collaborator can attach these labels to any pull request/issue. As commits land on the staging branches, the backporter removes the `lts-watch-` label. Likewise, as commits land in an LTS release, the releaser removes the `land-on-` label. Attach the appropriate `lts-watch-` label to any pull request that might impact an LTS release. ## Who to CC in the issue tracker \| Subsystem \| Maintainers \| \| -------------------------------------------------------------------------- \| ----------------------------------------------------------------------------- \| \| `benchmark/` \| @nodejs/benchmarking, @mscdex \| \| `doc/`, `.md` \| @nodejs/documentation \| \| `lib/assert` \| @nodejs/assert \| \| `lib/async_hooks` \| @nodejs/async\_hooks for bugs/reviews (+ @nodejs/diagnostics for API) \| \| `lib/buffer` \| @nodejs/buffer \| \| `lib/child_process` \| @nodejs/child\_process \| \| `lib/cluster` \| @nodejs/cluster \| \| `lib/{crypto,tls,https}` \| @nodejs/crypto \| \| `lib/dgram` \| @nodejs/dgram \| \| `lib/domains` \| @nodejs/domains \| \| `lib/fs`, `src/{fs,file}` \| @nodejs/fs \| \| `lib/{_}http{}` \| @nodejs/http \| \| `lib/inspector.js`, `src/inspector_` \| @nodejs/v8-inspector \| \| `lib/internal/bootstrap/` \| @nodejs/process \| \| `lib/internal/url`, `src/node_url` \| @nodejs/url \| \| `lib/net` \| @bnoordhuis, @indutny, @nodejs/streams \| \| `lib/repl` \| @nodejs/repl \| \| `lib/{_}stream{}` \| @nodejs/streams \| \| `lib/internal/test_runner` \| @nodejs/test\_runner \| \| `lib/timers` \| @nodejs/timers \| \| `lib/util` \| @nodejs/util \| \| `lib/zlib` \| @nodejs/zlib \| \| `src/async_wrap.` \| @nodejs/async\_hooks \| \| `src/node_api.` \| @nodejs/node-api \| \| `src/node_crypto.`, `src/crypto` \| @nodejs/crypto \| \| `test/` \| @nodejs/testing \| \| `tools/node_modules/eslint`, `.eslintrc` \| @nodejs/linting \| \| build \| @nodejs/build \| \| `src/module_wrap.`, `lib/internal/modules/`, `lib/internal/vm/module.js` \| @nodejs/modules \| \| GYP \| @nodejs/gyp \| \| performance \| @nodejs/performance \| \| platform specific \| @nodejs/platform-{aix,arm,freebsd,macos,ppc,smartos,s390,windows,windows-arm} \| \| python code \| @nodejs/python \| \| upgrading c-ares \| @rvagg \| \| upgrading http-parser \| @nodejs/http, @nodejs/http2 \| \| upgrading libuv \| @nodejs/libuv \| \| upgrading npm \| @nodejs/npm \| \| upgrading V8 \| @nodejs/V8, @nodejs/post-mortem \| \| Embedded use or delivery of Node.js \| @nodejs/delivery-channels \| When things need extra attention, are controversial, or `semver-major`: @nodejs/tsc If you cannot find who to cc for a file, `git shortlog -n -s <file>` can help. ## Labels ### General labels * `confirmed-bug`: Bugs you have verified * `discuss`: Things that need larger discussion * `fast-track`: PRs that need to land faster - see [Waiting for approvals](#waiting-for-approvals) * `feature request`: Any issue that requests a new feature * `good first issue`: Issues suitable for newcomers to fix * `meta`: Governance, policies, procedures, etc. * `request-ci`: When this label is added to a PR, CI will be started automatically. See [Starting a Jenkins CI job](#starting-a-jenkins-ci-job) * `tsc-agenda`: Open issues and pull requests with this label will be added to the Technical Steering Committee meeting agenda *** * `author-ready` - A pull request is _author ready_ when: * There is a CI run in progress or completed. * There is at least one collaborator approval (or two TSC approvals for semver-major pull requests). * There are no outstanding review comments. Please always add the `author ready` label to pull requests that qualify. Please always remove it again as soon as the conditions are not met anymore, such as if the CI run fails or a new outstanding review comment is posted. *** * `semver-{minor,major}` * be conservative – that is, if a change has the remote _chance_ of breaking something, go for semver-major * when adding a semver label, add a comment explaining why you're adding it * minor vs. patch: roughly: "does it add a new method / does it add a new section to the docs" * major vs. everything else: run last versions tests against this version, if they pass, probably minor or patch ### LTS/version labels We use labels to keep track of which branches a commit should land on: * `dont-land-on-v?.x` * For changes that do not apply to a certain release line * Also used when the work of backporting a change outweighs the benefits * `land-on-v?.x` * Used by releasers to mark a pull request as scheduled for inclusion in an LTS release * Applied to the original pull request for clean cherry-picks, to the backport pull request otherwise * `backport-requested-v?.x` * Used to indicate that a pull request needs a manual backport to a branch in order to land the changes on that branch * Typically applied by a releaser when the pull request does not apply cleanly or it breaks the tests after applying * Will be replaced by either `dont-land-on-v?.x` or `backported-to-v?.x` * `backported-to-v?.x` * Applied to pull requests for which a backport pull request has been merged * `lts-watch-v?.x` * Applied to pull requests which the Release working group should consider including in an LTS release * Does not indicate that any specific action will be taken, but can be effective as messaging to non-collaborators * `release-agenda` * For things that need discussion by the Release working group * (for example semver-minor changes that need or should go into an LTS release) * `v?.x` * Automatically applied to changes that do not target `main` but rather the `v?.x-staging` branch Once a release line enters maintenance mode, the corresponding labels do not need to be attached anymore, as only important bugfixes will be included. ### Other labels * Operating system labels * `macos`, `windows`, `smartos`, `aix`, `linux`, etc. * Architecture labels * `arm`, `mips`, `s390`, `ppc`, etc. * No `x86{_64}` label because it is the implied default ["Merge pull request"]: https://help.github.com/articles/merging-a-pull-request/#merging-a-pull-request-on-github [Deprecation]: https://en.wikipedia.org/wiki/Deprecation [SECURITY.md]: https://github.com/nodejs/node/blob/HEAD/SECURITY.md [Stability Index]: ../api/documentation.md#stability-index [TSC]: https://github.com/nodejs/TSC [`--pending-deprecation`]: ../api/cli.md#--pending-deprecation [`--throw-deprecation`]: ../api/cli.md#--throw-deprecation [`@node-core/utils`]: https://github.com/nodejs/node-core-utils [backporting guide]: backporting-to-release-lines.md [commit message guidelines]: pull-requests.md#commit-message-guidelines [commit-example]: https://github.com/nodejs/node/commit/b636ba8186 [commit-queue.md]: ./commit-queue.md [git-email]: https://help.github.com/articles/setting-your-commit-email-address-in-git/ [git-node]: https://github.com/nodejs/node-core-utils/blob/HEAD/docs/git-node.md [git-node-metadata]: https://github.com/nodejs/node-core-utils/blob/HEAD/docs/git-node.md#git-node-metadata [git-username]: https://help.github.com/articles/setting-your-username-in-git/ [node-core-utils-credentials]: https://github.com/nodejs/node-core-utils#setting-up-credentials [node-core-utils-issues]: https://github.com/nodejs/node-core-utils/issues [unreliable tests]: https://github.com/nodejs/node/issues?q=is%3Aopen+is%3Aissue+label%3A%22CI+%2F+flaky+test%22	45.35 KB	2025-02-28 19:16
📄 commit-queue.md # Commit queue > Stability: 1 - Experimental _tl;dr: You can land pull requests by adding the `commit-queue` label to it._ Commit Queue is an experimental feature for the project which simplifies the landing process by automating it via GitHub Actions. With it, collaborators can land pull requests by adding the `commit-queue` label to a PR. All checks will run via `@node-core/utils`, and if the pull request is ready to land, the Action will rebase it and push to `main`. This document gives an overview of how the Commit Queue works, as well as implementation details, reasoning for design choices, and current limitations. ## Overview From a high-level, the Commit Queue works as follow: 1. Collaborators will add `commit-queue` label to pull requests ready to land 2. Every five minutes the queue will do the following for each pull request with the label: 1. Check if the PR also has a `request-ci` label (if it has, skip this PR since it's pending a CI run) 2. Check if the last Jenkins CI is finished running (if it is not, skip this PR) 3. Remove the `commit-queue` label 4. Run `git node land <pr> --oneCommitMax` 5. If it fails: 1. Abort `git node land` session 2. Add `commit-queue-failed` label to the PR 3. Leave a comment on the PR with the output from `git node land` 4. Skip next steps, go to next PR in the queue 6. If it succeeds: 1. Push the changes to nodejs/node 2. Leave a comment on the PR with `Landed in ...` 3. Close the PR 4. Go to next PR in the queue To make the Commit Queue squash all the commits of a pull request into the first one, add the `commit-queue-squash` label. To make the Commit Queue land a pull request containing several commits, add the `commit-queue-rebase` label. When using this option, make sure that all commits are self-contained, meaning every commit should pass all tests. ## Current limitations The Commit Queue feature is still in early stages, and as such it might not work for more complex pull requests. These are the currently known limitations of the commit queue: 1. All commits in a pull request must either be following commit message guidelines or be a valid [`fixup!`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---fixupamendrewordltcommitgt) commit that will be correctly handled by the [`--autosquash`](https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---autosquash) option 2. A CI must've ran and succeeded since the last change on the PR 3. A collaborator must have approved the PR since the last change 4. Only Jenkins CI and GitHub Actions are checked (V8 CI and CITGM are ignored) ## Implementation The [action](../../.github/workflows/commit-queue.yml) will run on scheduler events every five minutes. Five minutes is the smallest number accepted by the scheduler. The scheduler is not guaranteed to run every five minutes, it might take longer between runs. Using the scheduler is preferable over using pull\_request\_target for two reasons: 1. if two Commit Queue Actions execution overlap, there's a high-risk that the last one to finish will fail because the local branch will be out of sync with the remote after the first Action pushes. `issue_comment` event has the same limitation. 2. `pull_request_target` will only run if the Action exists on the base commit of a pull request, and it will run the Action version present on that commit, meaning we wouldn't be able to use it for already opened PRs without rebasing them first. `@node-core/utils` is configured with a personal token and a Jenkins token from [@nodejs-github-bot](https://github.com/nodejs/github-bot). `octokit/graphql-action` is used to fetch all pull requests with the `commit-queue` label. The output is a JSON payload, so `jq` is used to turn that into a list of PR ids we can pass as arguments to [`commit-queue.sh`](../../tools/actions/commit-queue.sh). > The personal token only needs permission for public repositories and to read > profiles, we can use the GITHUB\_TOKEN for write operations. Jenkins token is > required to check CI status. `commit-queue.sh` receives the following positional arguments: 1. The repository owner 2. The repository name 3. The Action GITHUB\_TOKEN 4. Every positional argument starting at this one will be a pull request ID of a pull request with commit-queue set. The script will iterate over the pull requests. `ncu-ci` is used to check if the last CI is still pending, and calls to the GitHub API are used to check if the PR is waiting for CI to start (`request-ci` label). The PR is skipped if CI is pending. No other CI validation is done here since `git node land` will fail if the last CI failed. The script removes the `commit-queue` label. It then runs `git node land`, forwarding stdout and stderr to a file. If any errors happen, `git node land --abort` is run, and then a `commit-queue-failed` label is added to the PR, as well as a comment with the output of `git node land`. If no errors happen during `git node land`, the script will use the `GITHUB_TOKEN` to push the changes to `main`, and then will leave a `Landed in ...` comment in the PR, and then will close it. Iteration continues until all PRs have done the steps above. ## Reverting broken commits Reverting broken commits is done manually by collaborators, just like when commits are landed manually via `git node land`. An easy way to revert is a good feature for the project, but is not explicitly required for the Commit Queue to work because the Action lands PRs just like collaborators do today. If once we start using the Commit Queue we notice that the number of required reverts increases drastically, we can pause the queue until a Revert Queue is implemented, but until then we can enable the Commit Queue and then work on a Revert Queue as a follow-up.	5.76 KB	2025-02-28 19:16
📄 components-in-core.md # To be or not to be in core This document explains things to consider when deciding whether a component should be in core or not. A component may be included in core as a dependency, a module, or integrated into the code base. The same arguments for including/not including in core generally apply in all of these cases. ## Strong arguments for including a component in core 1. The component provides functionality that is standardized (such as a [Web API][]) and overlaps with existing functionality. 2. The component can only be implemented in core. 3. The component can only be implemented in a performant way in core. 4. Developer experience is significantly improved if the component is in core. 5. The component provides functionality that can be expected to solve at least one common use case Node.js users face. 6. The component requires native bindings. Inclusion in core enables utility across operating systems and architectures without requiring users to have a native compilation toolchain. 7. Part or all of the component will also be re-used or duplicated in core. ## Strong arguments against including a component in core 1. None of the arguments listed in the previous section apply. 2. The component has a license that prohibits Node.js from including it in core without also changing its own license. 3. There is already similar functionality in core and adding the component will provide a second API to do the same thing. 4. A component (or/and the standard it is based on) is deprecated and there is a non-deprecated alternative. 5. The component is evolving quickly and inclusion in core will require frequent API changes. ## Benefits and challenges When it is unclear whether a component should be included in core, it might be helpful to consider these additional factors. ### Benefits 1. The component will receive more frequent testing with Node.js CI and CITGM. 2. The component will be integrated into the LTS workflow. 3. Documentation will be integrated with core. 4. There is no dependency on npm. ### Challenges 1. Inclusion in core, rather than as an ecosystem module, is likely to reduce code merging velocity. The Node.js process for code review and merging is more time-consuming than that of most separate modules. 2. By being bound to the Node.js release cycle, it is harder and slower to publish patches. 3. Less flexibility for users. They can't update the component when they choose without also updating Node.js. [Web API]: https://developer.mozilla.org/en-US/docs/Web/API	2.51 KB	2025-02-28 19:16
📄 cpp-style-guide.md # C++ style guide See also the [C++ codebase README](../../src/README.md) for C++ idioms in the Node.js codebase not related to stylistic issues. ## Table of contents * [Guides and references](#guides-and-references) * [Formatting](#formatting) * [Left-leaning (C++ style) asterisks for pointer declarations](#left-leaning-c-style-asterisks-for-pointer-declarations) * [C++ style comments](#c-style-comments) * [2 spaces of indentation for blocks or bodies of conditionals](#2-spaces-of-indentation-for-blocks-or-bodies-of-conditionals) * [4 spaces of indentation for statement continuations](#4-spaces-of-indentation-for-statement-continuations) * [Align function arguments vertically](#align-function-arguments-vertically) * [Initialization lists](#initialization-lists) * [PascalCase for methods, functions, and classes](#pascalcase-for-methods-functions-and-classes) * [`snake_case` for local variables and parameters](#snake_case-for-local-variables-and-parameters) * [`snake_case_` for private class fields](#snake_case_-for-private-class-fields) * [`snake_case` for C-like structs](#snake_case-for-c-like-structs) * [Space after `template`](#space-after-template) * [Memory management](#memory-management) * [Memory allocation](#memory-allocation) * [Use `nullptr` instead of `NULL` or `0`](#use-nullptr-instead-of-null-or-0) * [Use explicit pointer comparisons](#use-explicit-pointer-comparisons) * [Ownership and smart pointers](#ownership-and-smart-pointers) * [Avoid non-const references](#avoid-non-const-references) * [Use AliasedBuffers to manipulate TypedArrays](#use-aliasedbuffers-to-manipulate-typedarrays) * [Others](#others) * [Type casting](#type-casting) * [Using `auto`](#using-auto) * [Do not include `.h` if `-inl.h` has already been included](#do-not-include-h-if--inlh-has-already-been-included) * [Avoid throwing JavaScript errors in C++ methods](#avoid-throwing-javascript-errors-in-c) * [Avoid throwing JavaScript errors in nested C++ methods](#avoid-throwing-javascript-errors-in-nested-c-methods) ## Guides and references The Node.js C++ codebase strives to be consistent in its use of language features and idioms, as well as have some specific guidelines for the use of runtime features. Coding guidelines are based on the following guides (highest priority first): 1. This document. 2. The [Google C++ Style Guide][]. 3. The ISO [C++ Core Guidelines][]. In general, code should follow the C++ Core Guidelines, unless overridden by the Google C++ Style Guide or this document. At the moment these guidelines are checked manually by reviewers with the goal to validate this with automatic tools. ## Formatting Unfortunately, the C++ linter (based on [Google's `cpplint`][]), which can be run explicitly via `make lint-cpp`, does not currently catch a lot of rules that are specific to the Node.js C++ code base. This document explains the most common of these rules: ### Left-leaning (C++ style) asterisks for pointer declarations `char* buffer;` instead of `char buffer;` ### C++ style comments Use C++ style comments (`//`) for both single-line and multi-line comments. Comments should also start with uppercase and finish with a dot. Examples: ```cpp // A single-line comment. // Multi-line comments // should also use C++ // style comments. ``` The codebase may contain old C style comments (`/ /`) from before this was the preferred style. Feel free to update old comments to the preferred style when working on code in the immediate vicinity or when changing/improving those comments. ### 2 spaces of indentation for blocks or bodies of conditionals ```cpp if (foo) bar(); ``` or ```cpp if (foo) { bar(); baz(); } ``` Braces are optional if the statement body only has one line. `namespace`s receive no indentation on their own. ### 4 spaces of indentation for statement continuations ```cpp VeryLongTypeName very_long_result = SomeValueWithAVeryLongName + SomeOtherValueWithAVeryLongName; ``` Operators are before the line break in these cases. ### Align function arguments vertically ```cpp void FunctionWithAVeryLongName(int parameter_with_a_very_long_name, double other_parameter_with_a_very_long_name, ...); ``` If that doesn't work, break after the `(` and use 4 spaces of indentation: ```cpp void FunctionWithAReallyReallyReallyLongNameSeriouslyStopIt( int okay_there_is_no_space_left_in_the_previous_line, ...); ``` ### Initialization lists Long initialization lists are formatted like this: ```cpp HandleWrap::HandleWrap(Environment env, Local<Object> object, uv_handle_t* handle, AsyncWrap::ProviderType provider) : AsyncWrap(env, object, provider), state_(kInitialized), handle_(handle) { ``` ### PascalCase for methods, functions, and classes Exceptions are simple getters/setters, which are named `property_name()` and `set_property_name()`, respectively. ```cpp class FooBar { public: void DoSomething(); static void DoSomethingButItsStaticInstead(); void set_foo_flag(int flag_value); int foo_flag() const; // Use const-correctness whenever possible. }; ``` ### `snake_case` for local variables and parameters ```cpp int FunctionThatDoesSomething(const char* important_string) { const char* pointer_into_string = important_string; } ``` ### `snake_case_` for private class fields ```cpp class Foo { private: int counter_ = 0; }; ``` ### `snake_case` for C-like structs For plain C-like structs snake\_case can be used. ```cpp struct foo_bar { int name; }; ``` ### Space after `template` ```cpp template <typename T> class FancyContainer { ... }; ``` ## Memory management ### Memory allocation * `Malloc()`, `Calloc()`, etc. from `util.h` abort in Out-of-Memory situations * `UncheckedMalloc()`, etc. return `nullptr` in OOM situations ### Use `nullptr` instead of `NULL` or `0` Further reading in the [C++ Core Guidelines][ES.47]. ### Use explicit pointer comparisons Use explicit comparisons to `nullptr` when testing pointers, i.e. `if (foo == nullptr)` instead of `if (foo)` and `foo != nullptr` instead of `!foo`. ### Ownership and smart pointers * [R.20][]: Use `std::unique_ptr` or `std::shared_ptr` to represent ownership * [R.21][]: Prefer `unique_ptr` over `shared_ptr` unless you need to share ownership Use `std::unique_ptr` to make ownership transfer explicit. For example: ```cpp std::unique_ptr<Foo> FooFactory(); void FooConsumer(std::unique_ptr<Foo> ptr); ``` Since `std::unique_ptr` has only move semantics, passing one by value transfers ownership to the callee and invalidates the caller's instance. Don't use `std::auto_ptr`, it is deprecated ([Reference][cppref_auto_ptr]). ### Avoid non-const references Using non-const references often obscures which values are changed by an assignment. Consider using a pointer instead, which requires more explicit syntax to indicate that modifications take place. ```cpp class ExampleClass { public: explicit ExampleClass(OtherClass* other_ptr) : pointer_to_other_(other_ptr) {} void SomeMethod(const std::string& input_param, std::string* in_out_param); // Pointer instead of reference const std::string& get_foo() const { return foo_string_; } void set_foo(const std::string& new_value) { foo_string_ = new_value; } void ReplaceCharacterInFoo(char from, char to) { // A non-const reference is okay here, because the method name already tells // users that this modifies 'foo_string_' -- if that is not the case, // it can still be better to use an indexed for loop, or leave appropriate // comments. for (char& character : foo_string_) { if (character == from) character = to; } } private: std::string foo_string_; // Pointer instead of reference. If this object 'owns' the other object, // this should be a `std::unique_ptr<OtherClass>`; a // `std::shared_ptr<OtherClass>` can also be a better choice. OtherClass* pointer_to_other_; }; ``` ### Use AliasedBuffers to manipulate TypedArrays When working with typed arrays that involve direct data modification from C++, use an `AliasedBuffer` when possible. The API abstraction and the usage scope of `AliasedBuffer` are documented in [aliased\_buffer.h][aliased_buffer.h]. ```cpp // Create an AliasedBuffer. AliasedBuffer<uint32_t, v8::Uint32Array> data; ... // Modify the data through natural operator semantics. data[0] = 12345; ``` ## Others ### Type casting * Use `static_cast<T>` if casting is required, and it is valid. * Use `reinterpret_cast` only when it is necessary. * Avoid C-style casts (`(type)value`). * `dynamic_cast` does not work because Node.js is built without [Run Time Type Information][]. Further reading: * [ES.48][]: Avoid casts * [ES.49][]: If you must use a cast, use a named cast ### Using `auto` Being explicit about types is usually preferred over using `auto`. Use `auto` to avoid type names that are noisy, obvious, or unimportant. When doing so, keep in mind that explicit types often help with readability and verifying the correctness of code. ```cpp for (const auto& item : some_map) { const KeyType& key = item.first; const ValType& value = item.second; // The rest of the loop can now just refer to key and value, // a reader can see the types in question, and we've avoided // the too-common case of extra copies in this iteration. } ``` ### Do not include `.h` if `-inl.h` has already been included Do: ```cpp #include "util-inl.h" // already includes util.h ``` Instead of: ```cpp #include "util.h" #include "util-inl.h" ``` ### Avoid throwing JavaScript errors in C++ When there is a need to throw errors from a C++ binding method, try to return the data necessary for constructing the errors to JavaScript, then construct and throw the errors [using `lib/internal/errors.js`][errors]. In general, type-checks on arguments should be done in JavaScript before the arguments are passed into C++. Then in the C++ binding, simply using `CHECK` assertions to guard against invalid arguments should be enough. If the return value of the binding cannot be used to signal failures or return the necessary data for constructing errors in JavaScript, pass a context object to the binding and put the necessary data inside in C++. For example: ```cpp void Foo(const FunctionCallbackInfo<Value>& args) { Environment* env = Environment::GetCurrent(args); // Let the JavaScript handle the actual type-checking, // only assertions are placed in C++ CHECK_EQ(args.Length(), 2); CHECK(args[0]->IsString()); CHECK(args[1]->IsObject()); int err = DoSomethingWith(args[0].As<String>()); if (err) { // Put the data inside the error context Local<Object> ctx = args[1].As<Object>(); Local<String> key = FIXED_ONE_BYTE_STRING(env->isolate(), "code"); ctx->Set(env->context(), key, err).FromJust(); } else { args.GetReturnValue().Set(something_to_return); } } // In the initialize function env->SetMethod(target, "foo", Foo); ``` ```js exports.foo = function(str) { // Prefer doing the type-checks in JavaScript if (typeof str !== 'string') { throw new errors.codes.ERR_INVALID_ARG_TYPE('str', 'string'); } const ctx = {}; const result = binding.foo(str, ctx); if (ctx.code !== undefined) { throw new errors.codes.ERR_ERROR_NAME(ctx.code); } return result; }; ``` #### Avoid throwing JavaScript errors in nested C++ methods When you need to throw a JavaScript exception from C++ (i.e. `isolate()->ThrowException()`), do it as close to the return to JavaScript as possible, and not inside of nested C++ calls. Since this changes the JavaScript execution state, doing it closest to where it is consumed reduces the chances of side effects. Node.js is built [without C++ exception handling][], so code using `throw` or even `try` and `catch` will break. [C++ Core Guidelines]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines [ES.47]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-nullptr [ES.48]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-casts [ES.49]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-casts-named [Google C++ Style Guide]: https://google.github.io/styleguide/cppguide.html [Google's `cpplint`]: https://github.com/google/styleguide [R.20]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rr-owner [R.21]: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rr-unique [Run Time Type Information]: https://en.wikipedia.org/wiki/Run-time_type_information [aliased_buffer.h]: https://github.com/nodejs/node/blob/HEAD/src/aliased_buffer.h#L12 [cppref_auto_ptr]: https://en.cppreference.com/w/cpp/memory/auto_ptr [errors]: https://github.com/nodejs/node/blob/HEAD/doc/contributing/using-internal-errors.md [without C++ exception handling]: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_exceptions.html#intro.using.exception.no	12.81 KB	2025-02-28 19:16
📄 diagnostic-tooling-support-tiers.md # Diagnostic tooling support tiers Diagnostic tooling is important to the consumers of Node.js. It is used both in development and in production in order to investigate problems. The failure of one of these tools may be as big a problem for an end user as a bug within the runtime itself. The Node.js project has assessed the tools and the APIs which support those tools. Each of the tools and APIs has been put into one of the following tiers. * Tier 1 - Must always be working (CI tests passing) for all Current and LTS Node.js releases. A release will not be shipped if the test suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release process. Tests on `main` will be run nightly when possible to provide early warning of potential issues. No commit to the current and LTS release branches should break this tool/API if the next major release is within 1 month. In addition: * The maintainers of the tool must remain responsive when there are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; * The tool must have a guide or other documentation in the Node.js GitHub organization or website; * The tool must be working on all supported platforms; * The tool must only be using APIs exposed by Node.js as opposed to its dependencies; * The tool must be open source. * Tier 2 - Must be working (CI tests passing) for all LTS releases. An LTS release will not be shipped if the test suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release process. In addition: * The maintainers of the tool must remain responsive when there are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; * The tool must have a guide or other documentation in the Node.js GitHub organization or website; * The tool must be open source. * Tier 3 - If possible its test suite will be run at least nightly in the Node.js CI or in CITGM, and issues opened for failures. Does not block shipping a release. * Tier 4 - Does not block shipping a release. * Unclassified - tool/API is new or does not have the required testing in the Node.js CI in order to qualify for a higher tier. The choice of which tier a particular tool will be assigned to, will be a collaborative decision between Diagnostics WG and Release WG. Some of the criteria considered might be: * If the tool fits into a key category as listed below. * Whether the tool is actively used by the ecosystem. * The availability of alternatives. * Impact to the overall ecosystem if the tool is not working. * The availability of reliable test suite that can be integrated into our CI. * The availability of maintainer or community collaborator who will help resolve issues when there are CI failures. * If the tool is maintained by the Node.js Foundation GitHub organization. The current categories of tools/APIs that fall under these Tiers are: * FFDC (F) - First failure data capture, easy to consume initial diagnostic information. * Tracing (T) - use of logging to provide information about execution flow. * Memory (M) - tools that provide additional information about memory used in the Heap or by native code. * Profiling (P) - tools that provide additional information about where CPU cycles are being spent. * AsyncFlow (A) - tools that provide additional insight into asynchronous execution flow. ## Adding a tool to this list Any tool that might be used to investigate issues when running Node.js can be added to the list. If there is a new tool that should be added to the list, it should start by being added to the "Not yet classified" or "Tier 4" lists. Once it has been added to the list "promotion" to Tier 3 through Tier 1 requires that the requirements listed above be met AND have agreement from Diagnostics WG and Release WG based on the criteria listed above. ## Tiers The tools are currently assigned to Tiers as follows: ## Tier 1 \| Tool Type \| Tool/API Name \| Regular Testing in Node.js CI \| Integrated with Node.js \| Target Tier \| \| --------- \| --------------------- \| ----------------------------- \| ----------------------- \| ----------- \| \| FFDC \| [diagnostic report][] \| Yes \| Yes \| 1 \| \| \| \| \| \| \| ## Tier 2 \| Tool Type \| Tool/API Name \| Regular Testing in Node.js CI \| Integrated with Node.js \| Target Tier \| \| --------- \| ------------- \| ----------------------------- \| ----------------------- \| ----------- \| \| \| \| \| \| \| ## Tier 3 \| Tool Type \| Tool/API Name \| Regular Testing in Node.js CI \| Integrated with Node.js \| Target Tier \| \| --------- \| ------------------------------------ \| ----------------------------- \| ----------------------- \| ----------- \| \| Profiling \| V8 CPU profiler \| Partial (V8 Tests) \| Yes \| 1 \| \| Profiling \| --prof/--prof-process flags \| Yes \| Yes \| 1 \| \| Profiling \| V8 CodeEventHandler API \| Partial (V8 Tests) \| Yes \| 2 \| \| Profiling \| V8 --interpreted-frames-native-stack \| Yes \| Yes \| 2 \| \| Profiling \| [Linux perf][] \| Yes \| Partial \| 2 \| \| Profiling \| [node-clinic][] \| No \| No \| 3 \| \| Debugger \| [Chrome Dev tools][] \| No \| No \| 3 \| ## Tier 4 \| Tool Type \| Tool/API Name \| Regular Testing in Node.js CI \| Integrated with Node.js \| Target Tier \| \| --------- \| ------------- \| ----------------------------- \| ----------------------- \| ----------- \| \| Profiling \| [0x][] \| No \| No \| 3 \| ## Not yet classified \| Tool Type \| Tool/API Name \| Regular Testing in Node.js CI \| Integrated with Node.js \| Target Tier \| \| --------- \| ----------------------------------------- \| ----------------------------- \| ----------------------- \| ----------- \| \| Memory \| V8 heap profiler \| No \| Yes \| 1 \| \| Memory \| V8 sampling heap profiler \| No \| Yes \| 1 \| \| AsyncFlow \| [Async Hooks (API)][] \| ? \| Yes \| 1 \| \| Debugger \| V8 Debug protocol (API) \| No \| Yes \| 1 \| \| Debugger \| [Command line Debug Client][] \| ? \| Yes \| 1 \| \| Tracing \| [trace\_events (API)][trace_events (API)] \| No \| Yes \| 1 \| \| Tracing \| trace\_gc \| No \| Yes \| 1 \| [0x]: https://github.com/davidmarkclements/0x [Async Hooks (API)]: https://nodejs.org/api/async_hooks.html [Chrome Dev Tools]: https://developer.chrome.com/docs/devtools/ [Command line Debug Client]: https://nodejs.org/api/inspector.html [Linux perf]: https://perf.wiki.kernel.org/index.php/Main_Page [diagnostic report]: https://nodejs.org/api/report.html [node-clinic]: https://github.com/clinicjs/node-clinic/ [trace_events (API)]: https://nodejs.org/api/tracing.html	8 KB	2025-02-28 19:16
📄 distribution.md # Node.js Distribution Policy This document describes some policies around what is and is not included in the Node.js distribution. ## Inclusion The Node.js distribution includes some external software that the Node.js project does not maintain. The choice to include a particular piece of software should not imply anything about that software relative to its competitors; in some cases, software was added when it had no competitors. While the Node.js project supports and encourages competition in the JavaScript ecosystem, as a policy, the Node.js project does not include multiple dependencies or tools that serve the same purpose. The following user-accessible external tools or libraries are the ones chosen for their particular purposes: * JavaScript engine: V8 * Package manager: `npm` * Package manager version manager: Corepack Being user-accessible, removal or replacement of these projects could happen only as a semver-major change, unless the related feature or project is documented as experimental. In addition, Node.js includes external projects as internal dependencies. These may be replaced or removed at any time, provided that doing so is not a breaking change.	1.16 KB	2025-02-28 19:16
📁 doc_img	-	2025-10-13 08:01
📄 feature-request-management.md # Feature request management Feature requests are a valuable source of input to the project. They help our maintainers understand what additions will be of value to users of the Node.js runtime. At the same time, the project is volunteer run and does not have the ability to direct resources toward specific work. The features which are implemented are those for which volunteers are individually motivated to work on. The best way to ensure a feature gets implemented is to create a PR to add it. The project strives to support people who do that. An open feature request does not provide any indication that work on that feature will take place and after some period of time may be detrimental as it may result in an expectation that will never be fulfilled. This process tries to balance retaining the valuable input we get through feature requests and the overhead of maintaining open feature requests that will never get implemented. ## Creating feature requests A feature request can be created by adding the `feature request` label to an issue. This may be done automatically when the issue is opened or at a later point (often when investigation of a bug report results in it being considered a feature request as opposed to a bug). The current list of feature requests can be found through the [is:issue is:open label:"feature request"](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22feature+request%22) query. ## Triage of feature requests There is no set process for triaging/handling feature requests. Individual collaborators review issues marked as `feature request` along with other issues and may or may not decide to work on an implementation or advocate on their behalf. If a collaborator believes a feature request must be implemented they can add the `never-stale` label to the issue and it will be excluded from the automated feature request handling as outlined below. ## Expressing support for a feature request If you come across a feature request and want to add your support for that feature please express your support with the thumbs up emoji as a reaction. At some point in the future we may use this as additional input in the automated handling of feature requests. ## Automated feature request handling Our experience is that most feature requests that are likely to be addressed, will be addressed within the first 6 months after they are submitted. Once there has been no activity on a feature request for 5 months, the following comment will be added to the issue: ```markdown There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md). ``` If there is no additional activity/discussion on the feature request in the next month, the following comment is added to the issue and the issue will be closed: ```markdown There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md). ```	3.41 KB	2025-02-28 19:16
📄 gn-build.md # GN Build Similar to GYP, GN is a build system designed for building Chromium. The official builds of Node.js are built with GYP, but GN build files are also provided as an unofficial alternative build system. The GN build files only support a subset of the Node.js build configurations. It's not required for all pull requests to Node.js to support GN builds, and the CI of Node.js does not currently test GN builds, though Node.js welcomes pull requests that improve GN support or fix breakages introduced by other pull requests. Currently the GN build is used by: 1. Electron for building Node.js together with Chromium. 2. V8 for testing the integration of Node.js in CI. ## Files for GN support Node.js contains following GN build files: * `node.gni` - Public GN arguments for configuring the build. * `/BUILD.gn` - This is the file where GN looks for build rules, in Node.js it just includes the `unofficial.gni` file to avoid accidental modifications. `/unofficial.gni` - The actual build rules for each component. ## Build with GN Unlike GYP, the GN tool does not include any built-in rules for compiling a project, which means projects building with GN must provide their own build configurations for things like how to invoke a C++ compiler. Chromium related projects like V8 and skia choose to reuse Chromium's build configurations, and V8's Node.js integration testing repository [`node-ci`][node-ci] can be reused for building Node.js. ### 1. Install `depot_tools` You'll need to install [`depot_tools`][depot-tools] the toolset used for fetching Chromium and its dependencies. ```bash git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git export PATH=/path/to/depot_tools:$PATH ``` You can ensure `depot_tools` is correctly added to your PATH by running `which gn` and confirming that it returns `/path/to/depot_tools/gn`. NOTE:* On Windows you'll also need to set the environment variable `DEPOT_TOOLS_WIN_TOOLCHAIN=0`. To do so, open `Control Panel` → `System and Security` → `System` → `Advanced system settings` and add a system variable `DEPOT_TOOLS_WIN_TOOLCHAIN` with value `0`. This tells `depot_tools` to use your locally installed version of Visual Studio (by default, `depot_tools` will try to download a Google-internal version that only Googlers have access to). ### 2. Checkout Node.js Source Code To check out the latest main branch of Node.js for building, use the `fetch` tool from `depot_tools`: ```bash mkdir node_gn cd node_gn fetch node ``` You can choose to save some time by omitting git history: ```bash fetch --no-history node ``` After syncing is done, you will get a directory structure like this: ```console node_gn/ ├── .gclient ├── .gclient_entries ├── ... └── node ├── DEPS ├── ... ├── build/ ├── node/ └── tools/ ``` The `node_gn` is a workspace directory, which only contains configurations and caches of the `gclient` tool from `depot_tools`, and the repository is checked out at `node_gn/node`. The `node_gn/node` directory is not a checkout of Node.js, it is actually [node-ci](https://chromium.googlesource.com/v8/node-ci/), the repository used by V8 for testing integration with Node.js. The source code of Node.js is checked out at `node_gn/node/node`. ### 3. Build GN only supports [`ninja`](https://ninja-build.org) for building. To build Node.js with GN you'll first need to generate `ninja` build files and then invoke `ninja` to perform the build. The `node-ci` repository provides a script for calling GN: ```bash cd node # Enter `node_gn/node` which contains a node-ci checkout ./tools/gn-gen.py out/Release ``` which writes `ninja` build files into the `out/Release` directory under `node_gn/node`. To see all possible configurable options, run `tools/gn-gen.py --help`. When `gn-gen.py` has executed successfully, you can then execute `ninja`: ```bash ninja -C out/Release node ``` After the build is completed, the compiled Node.js executable can be found in `out/Release/node`. ## Status of the GN build Currently the GN build of Node.js is not fully functioning. Some tests are still failing with the GN build, and there may be other small pitfall for certain configuration options. An effort is currently underway to make GN build work without using `depot_tools`, which is tracked in [#51689](https://github.com/nodejs/node/issues/51689). [depot-tools]: https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/depot_tools_tutorial.html#_setting_up [node-ci]: https://chromium.googlesource.com/v8/node-ci	4.54 KB	2025-02-28 19:16
📄 internal-api.md # Node.js Core Development Flags These flags are specifically designed for use in Node.js core development and are not intended for general application usage. > \[!NOTE] > These APIs are not bound by semantic versioning rules, and they can be altered or removed in any version of Node.js ## Command Line Interface (CLI) ### Flags #### `--debug-arraybuffer-allocations` Enables debugging of `ArrayBuffer` allocations. #### `--expose-internals` Allows the usage of `internal/*` modules, granting access to internal Node.js functionality. #### `--inspect-brk-node[=[host:]port]` Pauses execution at the start of Node.js application code, waiting for a debugger to connect on the specified `host` and `port`. This is useful for debugging application startup issues. If `host` and `port` are not provided, it defaults to `127.0.0.1:9229`. #### `--node-snapshot` Enables the use of Node.js snapshots, potentially improving startup performance. #### `--test-udp-no-try-send` Used for testing UDP functionality without attempting to send data. #### `--trace-promises` Enables tracing of promises for debugging and performance analysis. #### `--verify-base-objects` Allows verification of base objects for debugging purposes.	1.21 KB	2025-02-28 19:16
📄 investigating-native-memory-leaks.md # Investigating memory leaks with Valgrind A Node.js process may run out of memory due to excessive consumption of native memory. Native Memory is memory which is not managed by the V8 Garbage collector and is allocated either by the Node.js runtime, its dependencies or native [addons](https://nodejs.org/docs/latest/api/n-api.html). This guide provides information on how to use Valgrind to investigate these issues on Linux platforms. ## Valgrind [Valgrind](https://valgrind.org/docs/manual/quick-start.html) is a tool available on Linux distributions which can be used to investigate memory usage including identifying memory leaks (memory which is allocated and not freed) and other memory related problems like double freeing memory. To use Valgrind: * Be patient, running under Valgrind slows execution significantly due to the checks being performed. * Reduce your test case to the smallest reproduce. Due to the slowdown it is important to run the minimum test case in order to be able to do it in a reasonable time. ## Installation It is an optional package in most cases and must be installed explicitly. For example on Debian/Ubuntu: ```bash apt-get install valgrind ``` ## Invocation The simplest invocation of Valgrind is: ```bash valgrind node test.js ``` with the output being: ```console user1@minikube1:~/valgrind/node-addon-examples/1_hello_world/napi$ valgrind node test.js ==28993== Memcheck, a memory error detector ==28993== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==28993== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==28993== Command: node test.js ==28993== ==28993== Use of uninitialised value of size 8 ==28993== at 0x12F2279: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F3E9C: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0x12F3C77: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0xC7C9CF: v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate, v8::internal::(anonymous namespace)::InvokeParams const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0xC7CE87: v8::internal::Execution::Call(v8::internal::Isolate, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== by 0xB4CF3A: v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==28993== --28993-- WARNING: unhandled amd64-linux syscall: 332 --28993-- You may be able to write your own handler. --28993-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --28993-- Nevertheless we consider this a bug. Please report --28993-- it at http://valgrind.org/support/bug_reports.html. ==28993== ==28993== HEAP SUMMARY: ==28993== in use at exit: 6,140 bytes in 23 blocks ==28993== total heap usage: 12,888 allocs, 12,865 frees, 13,033,244 bytes allocated ==28993== ==28993== LEAK SUMMARY: ==28993== definitely lost: 0 bytes in 0 blocks ==28993== indirectly lost: 0 bytes in 0 blocks ==28993== possibly lost: 304 bytes in 1 blocks ==28993== still reachable: 5,836 bytes in 22 blocks ==28993== suppressed: 0 bytes in 0 blocks ==28993== Rerun with --leak-check=full to see details of leaked memory ==28993== ==28993== For counts of detected and suppressed errors, rerun with: -v ==28993== Use --track-origins=yes to see where uninitialised values come ``` This reports that Node.js is not _completely_ clean as there is some memory that was allocated but not freed when the process shut down. It is often impractical/not worth being completely clean in this respect. Modern operating systems will clean up the memory of the process after the shutdown while attempting to free all memory to get a clean report may have a negative impact on the code complexity and shutdown times. Node.js does a pretty good job only leaving on the order of 6 KB that are not freed on shutdown. ## An obvious memory leak Leaks can be introduced in native addons and the following is a simple example leak based on the "Hello world" addon from [node-addon-examples](https://github.com/nodejs/node-addon-examples). In this example, a loop which allocates approximately 1 MiB of memory and never frees it has been added: ```cpp void* malloc_holder = nullptr; napi_value Method(napi_env env, napi_callback_info info) { napi_status status; napi_value world; status = napi_create_string_utf8(env, "world", 5, &world); assert(status == napi_ok); // NEW LEAK HERE for (int i=0; i < 1024; i++) { malloc_holder = malloc(1024); } return world; } ``` When trying to create a memory leak you need to ensure that the compiler has not optimized out the code that creates the leak. For example, by assigning the result of the allocation to either a global variable or a variable that will be read afterwards the compiler will not optimize it out along with the malloc and Valgrind will properly report the memory leak. If `malloc_holder` in the example above is made into a local variable then the compiler may freely remove it along with the allocations (since it is not used) and Valgrind will not find any leaks since they will no longer exist in the code being run. Running Valgrind on this code shows the following: ```console user1@minikube1:~/valgrind/node-addon-examples/1_hello_world/napi$ valgrind node hello.js ==1504== Memcheck, a memory error detector ==1504== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1504== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==1504== Command: node hello.js ==1504== ==1504== Use of uninitialised value of size 8 ==1504== at 0x12F2279: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F3E9C: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0x12F3C77: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0xC7C9CF: v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate, v8::internal::(anonymous namespace)::InvokeParams const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0xC7CE87: v8::internal::Execution::Call(v8::internal::Isolate, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== by 0xB4CF3A: v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==1504== --1504-- WARNING: unhandled amd64-linux syscall: 332 --1504-- You may be able to write your own handler. --1504-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --1504-- Nevertheless we consider this a bug. Please report --1504-- it at http://valgrind.org/support/bug_reports.html. world ==1504== ==1504== HEAP SUMMARY: ==1504== in use at exit: 1,008,003 bytes in 1,032 blocks ==1504== total heap usage: 17,603 allocs, 16,571 frees, 18,306,103 bytes allocated ==1504== ==1504== LEAK SUMMARY: ==1504== definitely lost: 996,064 bytes in 997 blocks ==1504== indirectly lost: 0 bytes in 0 blocks ==1504== possibly lost: 3,304 bytes in 4 blocks ==1504== still reachable: 8,635 bytes in 31 blocks ==1504== of which reachable via heuristic: ==1504== multipleinheritance: 48 bytes in 1 blocks ==1504== suppressed: 0 bytes in 0 blocks ==1504== Rerun with --leak-check=full to see details of leaked memory ==1504== ==1504== For counts of detected and suppressed errors, rerun with: -v ==1504== Use --track-origins=yes to see where uninitialised values come from ==1504== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ``` Valgrind is reporting a problem as it shows 996,604 bytes as definitely lost and the question is how to find where that memory was allocated. The next step is to rerun as suggested in the output with `--leak-check=full`: ```bash user1@minikube1:~/valgrind/node-addon-examples/1_hello_world/napi$ valgrind --leak-check=full node hello.js ==4174== Memcheck, a memory error detector ==4174== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==4174== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==4174== Command: node hello.js ==4174== ==4174== Use of uninitialised value of size 8 ==4174== at 0x12F2279: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F3E9C: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F3C77: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xC7C9CF: v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate, v8::internal::(anonymous namespace)::InvokeParams const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xC7CE87: v8::internal::Execution::Call(v8::internal::Isolate, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xB4CF3A: v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== --4174-- WARNING: unhandled amd64-linux syscall: 332 --4174-- You may be able to write your own handler. --4174-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --4174-- Nevertheless we consider this a bug. Please report --4174-- it at http://valgrind.org/support/bug_reports.html. world ==4174== ==4174== HEAP SUMMARY: ==4174== in use at exit: 1,008,003 bytes in 1,032 blocks ==4174== total heap usage: 17,606 allocs, 16,574 frees, 18,305,977 bytes allocated ==4174== ==4174== 64 bytes in 1 blocks are definitely lost in loss record 17 of 35 ==4174== at 0x4C3017F: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x9AEAD5: napi_module_register (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x4010732: call_init (dl-init.c:72) ==4174== by 0x4010732: _dl_init (dl-init.c:119) ==4174== by 0x40151FE: dl_open_worker (dl-open.c:522) ==4174== by 0x5D052DE: _dl_catch_exception (dl-error-skeleton.c:196) ==4174== by 0x40147C9: _dl_open (dl-open.c:605) ==4174== by 0x4E3CF95: dlopen_doit (dlopen.c:66) ==4174== by 0x5D052DE: _dl_catch_exception (dl-error-skeleton.c:196) ==4174== by 0x5D0536E: _dl_catch_error (dl-error-skeleton.c:215) ==4174== by 0x4E3D734: _dlerror_run (dlerror.c:162) ==4174== by 0x4E3D050: dlopen@@GLIBC_2.2.5 (dlopen.c:87) ==4174== by 0x9B29A0: node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)::{lambda(node::binding::DLib)#1}::operator()(node::binding::DLib) const (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== ==4174== 304 bytes in 1 blocks are possibly lost in loss record 27 of 35 ==4174== at 0x4C31B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x40134A6: allocate_dtv (dl-tls.c:286) ==4174== by 0x40134A6: _dl_allocate_tls (dl-tls.c:530) ==4174== by 0x5987227: allocate_stack (allocatestack.c:627) ==4174== by 0x5987227: pthread_create@@GLIBC_2.2.5 (pthread_create.c:644) ==4174== by 0xAAF9DC: node::inspector::Agent::Start(std::string const&, node::DebugOptions const&, std::shared_ptr<node::HostPort>, bool) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x9A8BE7: node::Environment::InitializeInspector(std::unique_ptr<node::inspector::ParentInspectorHandle, std::default_delete<node::inspector::ParentInspectorHandle> >) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xA1C9A5: node::NodeMainInstance::CreateMainEnvironment(int) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xA1CB42: node::NodeMainInstance::Run() (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x9ACB67: node::Start(int, char) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x5BBFB96: (below main) (libc-start.c:310) ==4174== ==4174== 2,000 bytes in 2 blocks are possibly lost in loss record 33 of 35 ==4174== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x9794979: Method(napi_env__, napi_callback_info__) (in /home/user1/valgrind/node-addon-examples/1_hello_world/napi/build/Release/hello.node) ==4174== by 0x98F764: v8impl::(anonymous namespace)::FunctionCallbackWrapper::Invoke(v8::FunctionCallbackInfo<v8::Value> const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA6FC8: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA8DB6: v8::internal::Builtin_HandleApiCall(int, unsigned long, v8::internal::Isolate) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x1376358: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== ==4174== 997,000 bytes in 997 blocks are definitely lost in loss record 35 of 35 ==4174== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x9794979: Method(napi_env__, napi_callback_info__) (in /home/user1/valgrind/node-addon-examples/1_hello_world/napi/build/Release/hello.node) ==4174== by 0x98F764: v8impl::(anonymous namespace)::FunctionCallbackWrapper::Invoke(v8::FunctionCallbackInfo<v8::Value> const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA6FC8: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA8DB6: v8::internal::Builtin_HandleApiCall(int, unsigned long, v8::internal::Isolate) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x1376358: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== ==4174== LEAK SUMMARY: ==4174== definitely lost: 997,064 bytes in 998 blocks ==4174== indirectly lost: 0 bytes in 0 blocks ==4174== possibly lost: 2,304 bytes in 3 blocks ==4174== still reachable: 8,635 bytes in 31 blocks ==4174== of which reachable via heuristic: ==4174== multipleinheritance: 48 bytes in 1 blocks ==4174== suppressed: 0 bytes in 0 blocks ==4174== Reachable blocks (those to which a pointer was found) are not shown. ==4174== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==4174== ==4174== For counts of detected and suppressed errors, rerun with: -v ==4174== Use --track-origins=yes to see where uninitialised values come from ==4174== ERROR SUMMARY: 5 errors from 5 contexts (suppressed: 0 from 0) ``` This is the most interesting part of the report: ```console ==4174== 997,000 bytes in 997 blocks are definitely lost in loss record 35 of 35 ==4174== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x9794979: Method(napi_env__, napi_callback_info__) (in /home/user1/valgrind/node-addon-examples/1_hello_world/napi/build/Release/hello.node) ==4174== by 0x98F764: v8impl::(anonymous namespace)::FunctionCallbackWrapper::Invoke(v8::FunctionCallbackInfo<v8::Value> const&) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA6FC8: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xBA8DB6: v8::internal::Builtin_HandleApiCall(int, unsigned long, v8::internal::Isolate) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x1376358: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ``` From the stack trace we can tell that the leak came from a native addon: ```console ==4174== by 0x9794979: Method(napi_env__, napi_callback_info__) (in /home/user1/valgrind/node-addon-examples/1_hello_world/napi/build/Release/hello.node) ``` What we can't tell is where in the native addon the memory is being allocated. This is because by default the addon is compiled without the debug symbols which Valgrind needs to be able to provide more information. It is possible to hide leaks related to Node.js itself in future Valgrind runs using the suppression feature of Valgrind. ## Generating a Valgrind suppression file Valgrind uses suppression files to hide issues found from the summary. Generate a log file with embedded suppressions using the `--gen-suppressions` and `--log-file` flags: ```bash valgrind --leak-check=full \ --gen-suppressions=all \ --log-file=./valgrind-out.txt \ node hello.js ``` Valgrind will save the output to the log file specified. After each heap in the summary, Valgrind will include a suppression record: a structure that Valgrind can use to ignore specific memory issues. Suppression records can be saved to a suppression file which Valgrind can use in subsequent executions to hide various memory errors. This is an example of the suppression records from the previous call: ```text { <insert_a_suppression_name_here> Memcheck:Value8 obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node obj:/home/kevin/.nvm/versions/node/v12.14.1/bin/node fun:_ZN2v88internal12_GLOBAL__N_16InvokeEPNS0_7IsolateERKNS1_12InvokeParamsE fun:_ZN2v88internal9Execution4CallEPNS0_7IsolateENS0_6HandleINS0_6ObjectEEES6_iPS6_ fun:_ZN2v88Function4CallENS_5LocalINS_7ContextEEENS1_INS_5ValueEEEiPS5_ } { <insert_a_suppression_name_here> Memcheck:Leak match-leak-kinds: definite fun:_Znwm fun:napi_module_register fun:call_init.part.0 fun:call_init fun:_dl_init fun:_dl_catch_exception fun:dl_open_worker fun:_dl_catch_exception fun:_dl_open fun:dlopen_doit fun:_dl_catch_exception fun:_dl_catch_error fun:_dlerror_run } { <insert_a_suppression_name_here> Memcheck:Leak match-leak-kinds: possible fun:calloc fun:allocate_dtv fun:_dl_allocate_tls fun:allocate_stack fun:pthread_create@@GLIBC_2.2.5 fun:_ZN4node9inspector5Agent5StartERKSsRKNS_12DebugOptionsESt10shared_ptrINS_8HostPortEEb fun:_ZN4node11Environment19InitializeInspectorESt10unique_ptrINS_9inspector21ParentInspectorHandleESt14default_deleteIS3_EE fun:_ZN4node16NodeMainInstance21CreateMainEnvironmentEPi fun:_ZN4node16NodeMainInstance3RunEv fun:_ZN4node5StartEiPPc fun:(below main) } ``` Create a file (eg. `node-12.14.1.supp`) with the contents of the suppression records, and run Valgrind with the suppression file previously created: ```bash valgrind --leak-check=full \ --suppressions=./node-12.14.1.supp \ node hello.js ``` Now, the Valgrind leak summary for suppressed issues are only mentioned as `suppressed` in the leak summary: ```console ==12471== HEAP SUMMARY: ==12471== in use at exit: 8,067 bytes in 31 blocks ==12471== total heap usage: 16,482 allocs, 16,451 frees, 17,255,689 bytes allocated ==12471== ==12471== LEAK SUMMARY: ==12471== definitely lost: 0 bytes in 0 blocks ==12471== indirectly lost: 0 bytes in 0 blocks ==12471== possibly lost: 0 bytes in 0 blocks ==12471== still reachable: 7,699 bytes in 29 blocks ==12471== of which reachable via heuristic: ==12471== multipleinheritance: 48 bytes in 1 blocks ==12471== suppressed: 368 bytes in 2 blocks ``` ## Enabling debug symbols to get more information Leaks may be either in addons or Node.js itself. The sections which follow cover the steps needed to enable debug symbols to get more info. ### Native addons To enable debug symbols for all of your addons that are compiled on install use: ```bash npm install --debug ``` Any options which are not consumed by npm are passed on to node-gyp and this results in the addons being compiled with the debug option. If the native addon contains pre-built binaries you will need to force a rebuild. ```bash npm install --debug npm rebuild ``` The next step is to run Valgrind after the rebuild. This time the information for the leaking location includes the name of the source file and the line number: ```console ==18481== 997,000 bytes in 997 blocks are definitely lost in loss record 35 of 35 ==18481== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) >>>>> ==18481== by 0x9794989: Method(napi_env__, napi_callback_info__) (hello.cc:13) <<<<< ==18481== by 0x98F764: v8impl::(anonymous namespace)::FunctionCallbackWrapper::Invoke(v8::FunctionCallbackInfo<v8::Value> const&) (in /home/user1/val grind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0xBA6FC8: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal:: Isolate, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTem plateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0xBA8DB6: v8::internal::Builtin_HandleApiCall(int, unsigned long, v8::internal::Isolate) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x1376358: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==18481== by 0x12F68A3: ??? (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ``` This new output shows us exactly where the leak is occurring in the file `hello.cc`: ```cpp 6 void malloc_holder = nullptr; 7 napi_value Method(napi_env env, napi_callback_info info) { 8 napi_status status; 9 napi_value world; 10 status = napi_create_string_utf8(env, "world", 5, &world); 11 assert(status == napi_ok); 12 for (int i=0; i< 1000; i++) { 13 malloc_holder = malloc(1000); // <<<<<< This is where we are allocating the memory that is not freed 14 } 15 return world; 16 } ``` ### Node.js binary If the leak is not in an addon and is instead in the Node.js binary itself, you may need to compile node yourself and turn on debug symbols. Looking at this entry reported by Valgrind, with a release binary we see: ```console ==4174== 304 bytes in 1 blocks are possibly lost in loss record 27 of 35 ==4174== at 0x4C31B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4174== by 0x40134A6: allocate_dtv (dl-tls.c:286) ==4174== by 0x40134A6: _dl_allocate_tls (dl-tls.c:530) ==4174== by 0x5987227: allocate_stack (allocatestack.c:627) ==4174== by 0x5987227: pthread_create@@GLIBC_2.2.5 (pthread_create.c:644) ==4174== by 0xAAF9DC: node::inspector::Agent::Start(std::string const&, node::DebugOptions const&, std::shared_ptr<node::HostPort>, bool) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x9A8BE7: node::Environment::InitializeInspector(std::unique_ptr<node::inspector::ParentInspectorHandle, std::default_delete<node::inspector::ParentInspectorHandle> >) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xA1C9A5: node::NodeMainInstance::CreateMainEnvironment(int) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0xA1CB42: node::NodeMainInstance::Run() (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x9ACB67: node::Start(int, char) (in /home/user1/valgrind/node-v12.14.1-linux-x64/bin/node) ==4174== by 0x5BBFB96: (below main) (libc-start.c:310) ``` This gives us some information of where to look (`node::inspector::Agent::Start`) but not where in that function. We get more information than you might expect (or see by default with addons) because the Node.js binary exports many of its symbols using `-rdynamic` so that they can be used by addons. If the stack gives you enough information to track down where the leak is, that's great, otherwise the next step is to compile a debug build of Node.js. To get additional information with Valgrind: Check out the Node.js source corresponding to the release that you want to debug. For example: ```bash git clone https://github.com/nodejs/node.git git checkout v12.14.1 ``` * Compile with debug enabled (for additional info see [building a debug build](https://github.com/nodejs/node/blob/v12.14.1/BUILDING.md#building-a-debug-build)). For example, on \nix: ```bash ./configure --debug make -j4 ``` Make sure to run with your compiled debug version of Node.js. Having used `./configure --debug`, two binaries will have been built when `make` was run. You must use the one which is in `out/Debug`. Running Valgrind using the debug build of Node.js shows: ```console ==44112== 592 bytes in 1 blocks are possibly lost in loss record 26 of 27 ==44112== at 0x4C2BF79: calloc (vg_replace_malloc.c:762) ==44112== by 0x4012754: _dl_allocate_tls (in /usr/lib64/ld-2.17.so) ==44112== by 0x586287B: pthread_create@@GLIBC_2.2.5 (in /usr/lib64/libpthread-2.17.so) ==44112== by 0xFAB2D2: node::inspector::(anonymous namespace)::StartDebugSignalHandler() (inspector_agent.cc:140) ==44112== by 0xFACB10: node::inspector::Agent::Start(std::string const&, node::DebugOptions const&, std::shared_ptr<node::HostPort>, bool) (inspector_agent.cc:777) ==44112== by 0xE3A0BB: node::Environment::InitializeInspector(std::unique_ptr<node::inspector::ParentInspectorHandle, std::default_delete<node::inspector::ParentInspectorHandle> >) (node.cc:216) ==44112== by 0xEE8F3E: node::NodeMainInstance::CreateMainEnvironment(int) (node_main_instance.cc:222) ==44112== by 0xEE8831: node::NodeMainInstance::Run() (node_main_instance.cc:108) ==44112== by 0xE3CDEC: node::Start(int, char*) (node.cc:996) ==44112== by 0x22D8BBF: main (node_main.cc:126) ``` Now we can see the specific file name and line in the Node.js code which caused the allocation (inspector\_agent.cc:140). We can examine that line (and its surrounding code) to find a solution for the memory leak.	30.56 KB	2025-02-28 19:16
📄 issues.md # Issues * [Asking for general help](#asking-for-general-help) * [Discussing non-technical topics](#discussing-non-technical-topics) * [Submitting a bug report](#submitting-a-bug-report) * [Triaging a bug report](#triaging-a-bug-report) ## Asking for general help Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository][]. ## Discussing non-technical topics Discussion of non-technical topics (such as intellectual property and trademark) should be directed to the [Technical Steering Committee (TSC) repository][]. ## Submitting a bug report When opening a new issue in the `nodejs/node` issue tracker, users will be presented with a choice of issue templates. If you believe that you have uncovered a bug in Node.js, please fill out the `Bug Report` template to the best of your ability. Do not worry if you cannot answer every detail; just fill in what you can. The two most important pieces of information we need in order to properly evaluate the report is a description of the behavior you are seeing and a simple test case we can use to recreate the problem on our own. If we cannot recreate the issue, it becomes impossible for us to fix. In order to rule out the possibility of bugs introduced by userland code, test cases should be limited, as much as possible, to using _only_ Node.js APIs. If the bug occurs only when you're using a specific userland module, there is a very good chance that either (a) the module has a bug or (b) something in Node.js changed that broke the module. See [How to create a Minimal, Complete, and Verifiable example](https://stackoverflow.com/help/mcve). ## Triaging a bug report Once an issue has been opened, it is common for there to be discussion around it. Some contributors may have differing opinions about the issue, including whether the behavior being seen is a bug or a feature. This discussion is part of the process and should be kept focused, helpful, and professional. The objective of helping with triaging issues (in core and help repos) is to help reduce the issue backlog and keep the issue tracker healthy, while enabling newcomers another meaningful way to get engaged and contribute. Anyone with a reasonable understanding of Node.js programming and the project's GitHub organization plus a few contributions to the project (commenting on issues or PRs) can apply for and become a triager. Open a PR on the README.md of this project with: i) a request to be added as a triager, ii) the motivation for becoming a triager, and iii) agreement on reading, understanding, and adhering to the project's [Code Of Conduct](https://github.com/nodejs/admin/blob/HEAD/CODE_OF_CONDUCT.md). The triage role enables the ability to carry out the most common triage activities, such as applying labels and closing/reopening/assigning issues. For more information on the roles and permissions, see ["Permission levels for repositories owned by an organization"](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization). When triagging issues and PRs: * Show patience and empathy, especially to first-time contributors. * Show no patience towards spam or troll, close the issue without interacting with it and report the user to the moderation repository. * If you're not able to reproduce an issue, leave a comment asking for more info and add the `needs more info` label. * Ideally issues should be closed only when they have been fixed or answered (and merged for pull requests). Closing an issue (or PR) earlier can be seen as dismissive from the point of view of the reporter/author. Always try to communicate the reason for closing the issue/PR. [Node.js help repository]: https://github.com/nodejs/help/issues [Technical Steering Committee (TSC) repository]: https://github.com/nodejs/TSC/issues	3.94 KB	2025-02-28 19:16
📁 maintaining	-	2025-10-13 08:01
📄 node-postmortem-support.md # Postmortem support Postmortem metadata are constants present in the final build which can be used by debuggers and other tools to navigate through internal structures of software when analyzing its memory (either on a running process or a core dump). Node.js provides this metadata in its builds for V8 and Node.js internal structures. ## V8 postmortem metadata V8 prefixes all postmortem constants with `v8dbg_`, and they allow inspection of objects on the heap as well as object properties and references. V8 generates those symbols with a script (`deps/v8/tools/gen-postmortem-metadata.py`), and Node.js always includes these constants in the final build. ## Node.js debug symbols Node.js prefixes all postmortem constants with `nodedbg_`, and they complement V8 constants by providing ways to inspect Node.js-specific structures, like `node::Environment`, `node::BaseObject` and its descendants, classes from `src/utils.h` and others. Those constants are declared in `src/node_postmortem_metadata.cc`, and most of them are calculated at compile time. ### Calculating offset of class members Node.js constants referring to the offset of class members in memory are calculated at compile time. Because of that, those class members must be at a fixed offset from the start of the class. That's not a problem in most cases, but it also means that those members should always come after any templated member on the class definition. For example, if we want to add a constant with the offset for `ReqWrap::req_wrap_queue_`, it should be defined after `ReqWrap::req_`, because `sizeof(req_)` depends on the type of T, which means the class definition should be like this: ```cpp template <typename T> class ReqWrap : public AsyncWrap { private: // req_wrap_queue_ comes before any templated member, which places it in a // fixed offset from the start of the class ListNode<ReqWrap> req_wrap_queue_; T req_; }; ``` instead of: ```cpp template <typename T> class ReqWrap : public AsyncWrap { private: T req_; // req_wrap_queue_ comes after a templated member, which means it won't be in // a fixed offset from the start of the class ListNode<ReqWrap> req_wrap_queue_; }; ``` There are also tests on `test/cctest/test_node_postmortem_metadata.cc` to make sure all Node.js postmortem metadata are calculated correctly. ## Tools and references * [llnode](https://github.com/nodejs/llnode): LLDB plugin * [`mdb_v8`](https://github.com/joyent/mdb_v8): mdb plugin * [nodejs/post-mortem](https://github.com/nodejs/post-mortem): Node.js post-mortem working group	2.53 KB	2025-02-28 19:16
📄 offboarding.md # Offboarding This document is a checklist of things to do when a collaborator becomes emeritus or leaves the project. * Remove the collaborator from the [`@nodejs/collaborators`][] team. * Open a fast-track pull request to move the collaborator to the collaborator emeriti list in README.md. * Determine what GitHub teams the collaborator belongs to. In consultation with the collaborator, determine which of those teams they should be removed from. * Some teams may also require a pull request to remove the collaborator from a team listing. For example, if someone is removed from @nodejs/build, they should also be removed from the Build WG README.md file in the <https://github.com/nodejs/build> repository. * When in doubt, especially if you are unable to get in contact with the collaborator, remove them from all teams. It is easy enough to add them back later, so we err on the side of privacy and security. * Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub org unless they are members for a reason other than being a Collaborator. * [Open an issue](https://github.com/nodejs/build/issues/new) in the nodejs/build repository titled `Remove Collaborator from Coverity` asking that the collaborator be removed from the Node.js coverity project if they had access. [`@nodejs/collaborators`]: https://github.com/orgs/nodejs/teams/collaborators/members	1.39 KB	2025-02-28 19:16
📄 primordials.md # Usage of primordials in core The file `lib/internal/per_context/primordials.js` subclasses and stores the JS built-ins that come from the VM so that Node.js built-in modules do not need to later look these up from the global proxy, which can be mutated by users. For some area of the codebase, performance and code readability are deemed more important than reliability against prototype pollution: * `node:http` * `node:http2` * `node:tls` Usage of primordials should be preferred for new code in other areas, but replacing current code with primordials should be [done with care](#primordials-with-known-performance-issues). It is highly recommended to ping the relevant team when reviewing a pull request that touches one of the subsystems they "own". ## Accessing primordials The primordials are meant for internal use only, and are only accessible for internal core modules. User code cannot use or rely on primordials. It is usually fine to rely on ECMAScript built-ins and assume that it will behave as specified. If you would like to access the `primordials` object to help you with Node.js core development or for tinkering, you can expose it on the global scope using this combination of CLI flags: ```bash node --expose-internals -r internal/test/binding ``` ## Contents of primordials ### Properties of the global object Objects and functions on the global object can be deleted or replaced. Using them from primordials makes the code more reliable: ```js globalThis.Array === primordials.Array; // true globalThis.Array = function() { return [1, 2, 3]; }; globalThis.Array === primordials.Array; // false primordials.Array(0); // [] globalThis.Array(0); // [1,2,3] ``` ### Prototype methods ECMAScript provides a group of methods available on built-in objects that are used to interact with JavaScript objects. ```js const array = [1, 2, 3]; array.push(4); // Here `push` refers to %Array.prototype.push%. console.log(JSON.stringify(array)); // [1,2,3,4] // %Array.prototype%.push is modified in userland. Array.prototype.push = function push(val) { return this.unshift(val); }; array.push(5); // Now `push` refers to the modified method. console.log(JSON.stringify(array)); // [5,1,2,3,4] ``` Primordials wrap the original prototype functions with new functions that take the `this` value as the first argument: ```js const { ArrayPrototypePush, } = primordials; const array = [1, 2, 3]; ArrayPrototypePush(array, 4); console.log(JSON.stringify(array)); // [1,2,3,4] Array.prototype.push = function push(val) { return this.unshift(val); }; ArrayPrototypePush(array, 5); console.log(JSON.stringify(array)); // [1,2,3,4,5] ``` ### Safe classes Safe classes are classes that provide the same API as their equivalent class, but whose implementation aims to avoid any reliance on user-mutable code. Safe classes should not be exposed to user-land; use unsafe equivalent when dealing with objects that are accessible from user-land. ### Variadic functions There are some built-in functions that accept a variable number of arguments (e.g.: `Math.max`, `%Array.prototype.push%`). It is sometimes useful to provide the list of arguments as an array. You can use primordial function with the suffix `Apply` (e.g.: `MathMaxApply`, `ArrayPrototypePushApply`) to do that. ## Primordials with known performance issues One of the reasons why the current Node.js API is not completely tamper-proof is performance: sometimes the use of primordials can cause performance regressions with V8, which when in a hot code path, could significantly decrease the performance of code in Node.js. * Methods that mutate the internal state of arrays: * `ArrayPrototypePush` * `ArrayPrototypePop` * `ArrayPrototypeShift` * `ArrayPrototypeUnshift` * Methods of the function prototype: * `FunctionPrototypeBind` * `FunctionPrototypeCall`: creates performance issues when used to invoke super constructors. * `FunctionPrototype`: use `() => {}` instead when referencing a no-op function. * `SafeArrayIterator` * `SafeStringIterator` * `SafePromiseAll` * `SafePromiseAllSettled` * `SafePromiseAny` * `SafePromiseRace` * `SafePromisePrototypeFinally`: use `try {} finally {}` block instead. * `ReflectConstruct`: Also affects `Reflect.construct`. `ReflectConstruct` creates new types of classes inside functions. Instead consider creating a shared class. See [nodejs/performance#109](https://github.com/nodejs/performance/issues/109). In general, when sending or reviewing a PR that makes changes in a hot code path, use extra caution and run extensive benchmarks. ## Implicit use of user-mutable methods ### Unsafe array iteration There are many usual practices in JavaScript that rely on iteration. It's useful to be aware of them when dealing with arrays (or `TypedArray`s) in core as array iteration typically calls several user-mutable methods. This sections lists the most common patterns in which ECMAScript code relies non-explicitly on array iteration and how to avoid it. <details> <summary>Avoid for-of loops on arrays</summary> ```js for (const item of array) { console.log(item); } ``` This code is internally expanded into something that looks like: ```js { // 1. Lookup @@iterator property on `array` (user-mutable if user-provided). // 2. Lookup @@iterator property on %Array.prototype% (user-mutable). // 3. Call that function. const iterator = array[Symbol.iterator](); // 1. Lookup `next` property on `iterator` (doesn't exist). // 2. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). // 3. Call that function. let { done, value: item } = iterator.next(); while (!done) { console.log(item); // Repeat. ({ done, value: item } = iterator.next()); } } ``` Instead of utilizing iterators, you can use the more traditional but still very performant `for` loop: ```js for (let i = 0; i < array.length; i++) { console.log(array[i]); } ``` The following code snippet illustrates how user-land code could impact the behavior of internal modules: ```js // User-land Array.prototype[Symbol.iterator] = () => ({ next: () => ({ done: true }), }); // Core let forOfLoopBlockExecuted = false; let forLoopBlockExecuted = false; const array = [1, 2, 3]; for (const item of array) { forOfLoopBlockExecuted = true; } for (let i = 0; i < array.length; i++) { forLoopBlockExecuted = true; } console.log(forOfLoopBlockExecuted); // false console.log(forLoopBlockExecuted); // true ``` This only applies if you are working with a genuine array (or array-like object). If you are instead expecting an iterator, a for-of loop may be a better choice. </details> <details> <summary>Avoid array destructuring assignment on arrays</summary> ```js const [first, second] = array; ``` This is roughly equivalent to: ```js // 1. Lookup @@iterator property on `array` (user-mutable if user-provided). // 2. Lookup @@iterator property on %Array.prototype% (user-mutable). // 3. Call that function. const iterator = array[Symbol.iterator](); // 1. Lookup `next` property on `iterator` (doesn't exist). // 2. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). // 3. Call that function. const first = iterator.next().value; // Repeat. const second = iterator.next().value; ``` Instead you can use object destructuring: ```js const { 0: first, 1: second } = array; ``` or ```js const first = array[0]; const second = array[1]; ``` This only applies if you are working with a genuine array (or array-like object). If you are instead expecting an iterator, array destructuring is the best choice. </details> <details> <summary>Avoid spread operator on arrays</summary> ```js // 1. Lookup @@iterator property on `array` (user-mutable if user-provided). // 2. Lookup @@iterator property on %Array.prototype% (user-mutable). // 3. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). const arrayCopy = [...array]; func(...array); ``` Instead you can use other ECMAScript features to achieve the same result: ```js const arrayCopy = ArrayPrototypeSlice(array); ReflectApply(func, null, array); ``` </details> <details> <summary><code>%Array.prototype.concat%</code> looks up <code>@@isConcatSpreadable</code> property of the passed arguments and the <code>this</code> value.</summary> ```js { // Unsafe code example: // 1. Lookup @@isConcatSpreadable property on `array` (user-mutable if // user-provided). // 2. Lookup @@isConcatSpreadable property on `%Array.prototype% // (user-mutable). // 2. Lookup @@isConcatSpreadable property on `%Object.prototype% // (user-mutable). const array = []; ArrayPrototypeConcat(array); } ``` ```js // User-land Object.defineProperty(Object.prototype, Symbol.isConcatSpreadable, { get() { this.push(5); return true; }, }); // Core { // Using ArrayPrototypeConcat does not produce the expected result: const a = [1, 2]; const b = [3, 4]; console.log(ArrayPrototypeConcat(a, b)); // [1, 2, 5, 3, 4, 5] } { // Concatenating two arrays can be achieved safely, e.g.: const a = [1, 2]; const b = [3, 4]; // Using %Array.prototype.push% and `SafeArrayIterator` to get the expected // outcome: const concatArray = []; ArrayPrototypePush(concatArray, ...new SafeArrayIterator(a), ...new SafeArrayIterator(b)); console.log(concatArray); // [1, 2, 3, 4] // Or using `ArrayPrototypePushApply` if it's OK to mutate the first array: ArrayPrototypePushApply(a, b); console.log(a); // [1, 2, 3, 4] } ``` </details> <details> <summary><code>%Object.fromEntries%</code> iterate over an array</summary> ```js { // Unsafe code example: // 1. Lookup @@iterator property on `array` (user-mutable if user-provided). // 2. Lookup @@iterator property on %Array.prototype% (user-mutable). // 3. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). const obj = ObjectFromEntries(array); } { // Safe example using `SafeArrayIterator`: const obj = ObjectFromEntries(new SafeArrayIterator(array)); } { // Safe example without using `SafeArrayIterator`: const obj = {}; for (let i = 0; i < array.length; i++) { obj[array[i][0]] = array[i][1]; } // In a hot code path, this would be the preferred method. } ``` </details> <details> <summary><code>%Promise.all%</code>, <code>%Promise.allSettled%</code>, <code>%Promise.any%</code>, and <code>%Promise.race%</code> iterate over an array</summary> ```js // 1. Lookup @@iterator property on `array` (user-mutable if user-provided). // 2. Lookup @@iterator property on %Array.prototype% (user-mutable). // 3. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). // 4. Lookup `then` property on %Array.Prototype% (user-mutable). // 5. Lookup `then` property on %Object.Prototype% (user-mutable). PromiseAll([]); // unsafe // 1. Lookup `then` property on %Array.Prototype% (user-mutable). // 2. Lookup `then` property on %Object.Prototype% (user-mutable). PromiseAll(new SafeArrayIterator([])); // still unsafe SafePromiseAll([]); // still unsafe SafePromiseAllReturnVoid([]); // safe SafePromiseAllReturnArrayLike([]); // safe const array = [promise]; const set = new SafeSet().add(promise); // When running one of these functions on a non-empty iterable, it will also: // 1. Lookup `then` property on `promise` (user-mutable if user-provided). // 2. Lookup `then` property on `%Promise.prototype%` (user-mutable). // 3. Lookup `then` property on %Array.Prototype% (user-mutable). // 4. Lookup `then` property on %Object.Prototype% (user-mutable). PromiseAll(new SafeArrayIterator(array)); // unsafe PromiseAll(set); // unsafe SafePromiseAllReturnVoid(array); // safe SafePromiseAllReturnArrayLike(array); // safe // Some key differences between `SafePromise[...]` and `Promise[...]` methods: // 1. SafePromiseAll, SafePromiseAllSettled, SafePromiseAny, SafePromiseRace, // SafePromiseAllReturnArrayLike, SafePromiseAllReturnVoid, and // SafePromiseAllSettledReturnVoid support passing a mapperFunction as second // argument. SafePromiseAll(ArrayPrototypeMap(array, someFunction)); SafePromiseAll(array, someFunction); // Same as the above, but more efficient. // 2. SafePromiseAll, SafePromiseAllSettled, SafePromiseAny, SafePromiseRace, // SafePromiseAllReturnArrayLike, SafePromiseAllReturnVoid, and // SafePromiseAllSettledReturnVoid only support arrays and array-like // objects, not iterables. Use ArrayFrom to convert an iterable to an array. SafePromiseAllReturnVoid(set); // ignores set content. SafePromiseAllReturnVoid(ArrayFrom(set)); // works // 3. SafePromiseAllReturnArrayLike is safer than SafePromiseAll, however you // should not use them when its return value is passed to the user as it can // be surprising for them not to receive a genuine array. SafePromiseAllReturnArrayLike(array).then((val) => val instanceof Array); // false SafePromiseAll(array).then((val) => val instanceof Array); // true ``` </details> <details> <summary><code>%Map%</code>, <code>%Set%</code>, <code>%WeakMap%</code>, and <code>%WeakSet%</code> constructors iterate over an array</summary> ```js // User-land Array.prototype[Symbol.iterator] = () => ({ next: () => ({ done: true }), }); // Core // 1. Lookup @@iterator property on %Array.prototype% (user-mutable). // 2. Lookup `next` property on %ArrayIteratorPrototype% (user-mutable). const set = new SafeSet([1, 2, 3]); console.log(set.size); // 0 ``` ```js // User-land Array.prototype[Symbol.iterator] = () => ({ next: () => ({ done: true }), }); // Core const set = new SafeSet(); set.add(1).add(2).add(3); console.log(set.size); // 3 ``` </details> ### Promise objects <details> <summary><code>%Promise.prototype.finally%</code> looks up <code>then</code> property of the Promise instance</summary> ```js // User-land Promise.prototype.then = function then(a, b) { return Promise.resolve(); }; // Core let finallyBlockExecuted = false; PromisePrototypeFinally(somePromiseThatEventuallySettles, () => { finallyBlockExecuted = true; }); process.on('exit', () => console.log(finallyBlockExecuted)); // false ``` ```js // User-land Promise.prototype.then = function then(a, b) { return Promise.resolve(); }; // Core let finallyBlockExecuted = false; (async () => { try { return await somePromiseThatEventuallySettles; } finally { finallyBlockExecuted = true; } })(); process.on('exit', () => console.log(finallyBlockExecuted)); // true ``` </details> <details> <summary><code>%Promise.all%</code>, <code>%Promise.allSettled%</code>, <code>%Promise.any%</code>, and <code>%Promise.race%</code> look up <code>then</code> property of the Promise instances</summary> You can use safe alternatives from primordials that differ slightly from the original methods: * It expects an array (or array-like object) instead of an iterable. * It wraps each promise in `SafePromise` objects and wraps the result in a new `Promise` instance – which may come with a performance penalty. * It accepts a `mapperFunction` as second argument. * Because it doesn't look up `then` property, it may not be the right tool to handle user-provided promises (which may be instances of a subclass of `Promise`). ```js // User-land Promise.prototype.then = function then(a, b) { return Promise.resolve(); }; // Core let thenBlockExecuted = false; PromisePrototypeThen( PromiseAll(new SafeArrayIterator([PromiseResolve()])), () => { thenBlockExecuted = true; }, ); process.on('exit', () => console.log(thenBlockExecuted)); // false ``` ```js // User-land Promise.prototype.then = function then(a, b) { return Promise.resolve(); }; // Core let thenBlockExecuted = false; PromisePrototypeThen( SafePromiseAll([PromiseResolve()]), () => { thenBlockExecuted = true; }, ); process.on('exit', () => console.log(thenBlockExecuted)); // true ``` A common pattern is to map on the array of `Promise`s to apply some transformations, in that case it can be more efficient to pass a second argument rather than invoking `%Array.prototype.map%`. ```js SafePromiseAll(ArrayPrototypeMap(array, someFunction)); SafePromiseAll(array, someFunction); // Same as the above, but more efficient. ``` </details> ### (Async) Generator functions Generators and async generators returned by generator functions and async generator functions are relying on user-mutable methods; their use in core should be avoided. <details> <summary><code>%GeneratorFunction.prototype.prototype%.next</code> is user-mutable</summary> ```js // User-land Object.getPrototypeOf(function* () {}).prototype.next = function next() { return { done: true }; }; // Core function* someGenerator() { yield 1; yield 2; yield 3; } let loopCodeExecuted = false; for (const nb of someGenerator()) { loopCodeExecuted = true; } console.log(loopCodeExecuted); // false ``` </details> <details> <summary><code>%AsyncGeneratorFunction.prototype.prototype%.next</code> is user-mutable</summary> ```js // User-land Object.getPrototypeOf(async function* () {}).prototype.next = function next() { return new Promise(() => {}); }; // Core async function* someGenerator() { yield 1; yield 2; yield 3; } let finallyBlockExecuted = false; async () => { try { for await (const nb of someGenerator()) { // some code; } } finally { finallyBlockExecuted = true; } }; process.on('exit', () => console.log(finallyBlockExecuted)); // false ``` </details> ### Text processing #### Unsafe string methods \| The string method \| looks up the property \| \| ----------------------------- \| --------------------- \| \| `String.prototype.match` \| `Symbol.match` \| \| `String.prototype.matchAll` \| `Symbol.matchAll` \| \| `String.prototype.replace` \| `Symbol.replace` \| \| `String.prototype.replaceAll` \| `Symbol.replace` \| \| `String.prototype.search` \| `Symbol.search` \| \| `String.prototype.split` \| `Symbol.split` \| ```js // User-land RegExp.prototype[Symbol.replace] = () => 'foo'; String.prototype[Symbol.replace] = () => 'baz'; // Core console.log(StringPrototypeReplace('ber', /e/, 'a')); // 'foo' console.log(StringPrototypeReplace('ber', 'e', 'a')); // 'baz' console.log(RegExpPrototypeSymbolReplace(/e/, 'ber', 'a')); // 'bar' ``` #### Unsafe string iteration As with arrays, iterating over strings calls several user-mutable methods. Avoid iterating over strings when possible, or use `SafeStringIterator`. #### Unsafe `RegExp` methods Functions that lookup the `exec` property on the prototype chain: * `RegExp.prototype[Symbol.match]` * `RegExp.prototype[Symbol.matchAll]` * `RegExp.prototype[Symbol.replace]` * `RegExp.prototype[Symbol.search]` * `RegExp.prototype[Symbol.split]` * `RegExp.prototype.test` ```js // User-land RegExp.prototype.exec = () => null; // Core console.log(RegExpPrototypeTest(/o/, 'foo')); // false console.log(RegExpPrototypeExec(/o/, 'foo') !== null); // true console.log(RegExpPrototypeSymbolSearch(/o/, 'foo')); // -1 console.log(SafeStringPrototypeSearch('foo', /o/)); // 1 ``` #### Don't trust `RegExp` flags RegExp flags are not own properties of the regex instances, which means flags can be reset from user-land. <details> <summary>List of <code>RegExp</code> methods that look up properties from mutable getters</summary> \| `RegExp` method \| looks up the following flag-related properties \| \| ------------------------------ \| ------------------------------------------------------------------ \| \| `get RegExp.prototype.flags` \| `global`, `ignoreCase`, `multiline`, `dotAll`, `unicode`, `sticky` \| \| `RegExp.prototype[@@match]` \| `global`, `unicode` \| \| `RegExp.prototype[@@matchAll]` \| `flags` \| \| `RegExp.prototype[@@replace]` \| `global`, `unicode` \| \| `RegExp.prototype[@@split]` \| `flags` \| \| `RegExp.prototype.toString` \| `flags` \| </details> ```js // User-land Object.defineProperty(RegExp.prototype, 'global', { value: false }); // Core console.log(RegExpPrototypeSymbolReplace(/o/g, 'foo', 'a')); // 'fao' console.log(RegExpPrototypeSymbolReplace(hardenRegExp(/o/g), 'foo', 'a')); // 'faa' ``` ### Defining object own properties When defining property descriptor (to add or update an own property to a JavaScript object), be sure to always use a null-prototype object to avoid prototype pollution. ```js // User-land Object.prototype.get = function get() {}; // Core try { ObjectDefineProperty({}, 'someProperty', { value: 0 }); } catch (err) { console.log(err); // TypeError: Invalid property descriptor. } ``` ```js // User-land Object.prototype.get = function get() {}; // Core ObjectDefineProperty({}, 'someProperty', { __proto__: null, value: 0 }); console.log('no errors'); // no errors. ``` Same applies when trying to modify an existing property, e.g. trying to make a read-only property enumerable: ```js // User-land Object.prototype.value = 'Unrelated user-provided data'; // Core class SomeClass { get readOnlyProperty() { return 'genuine data'; } } ObjectDefineProperty(SomeClass.prototype, 'readOnlyProperty', { enumerable: true }); console.log(new SomeClass().readOnlyProperty); // Unrelated user-provided data ``` ```js // User-land Object.prototype.value = 'Unrelated user-provided data'; // Core const kEnumerableProperty = { __proto__: null, enumerable: true }; // In core, use const {kEnumerableProperty} = require('internal/util'); class SomeClass { get readOnlyProperty() { return 'genuine data'; } } ObjectDefineProperty(SomeClass.prototype, 'readOnlyProperty', kEnumerableProperty); console.log(new SomeClass().readOnlyProperty); // genuine data ``` ### Defining a `Proxy` handler When defining a `Proxy`, the handler object could be at risk of prototype pollution when using a plain object literal: ```js // User-land Object.prototype.get = () => 'Unrelated user-provided data'; // Core const objectToProxy = { someProperty: 'genuine value' }; const proxyWithPlainObjectLiteral = new Proxy(objectToProxy, { has() { return false; }, }); console.log(proxyWithPlainObjectLiteral.someProperty); // Unrelated user-provided data const proxyWithNullPrototypeObject = new Proxy(objectToProxy, { __proto__: null, has() { return false; }, }); console.log(proxyWithNullPrototypeObject.someProperty); // genuine value ``` ### Checking if an object is an instance of a class #### Using `instanceof` looks up the `@@hasInstance` property of the class ```js // User-land Object.defineProperty(Array, Symbol.hasInstance, { __proto__: null, value: () => true, }); Object.defineProperty(Date, Symbol.hasInstance, { __proto__: null, value: () => false, }); // Core const { FunctionPrototypeSymbolHasInstance, } = primordials; console.log(new Date() instanceof Array); // true console.log(new Date() instanceof Date); // false console.log(FunctionPrototypeSymbolHasInstance(Array, new Date())); // false console.log(FunctionPrototypeSymbolHasInstance(Date, new Date())); // true ``` Even without user mutations, the result of `instanceof` can be deceiving when dealing with values from different realms: ```js const vm = require('node:vm'); console.log(vm.runInNewContext('[]') instanceof Array); // false console.log(vm.runInNewContext('[]') instanceof vm.runInNewContext('Array')); // false console.log([] instanceof vm.runInNewContext('Array')); // false console.log(Array.isArray(vm.runInNewContext('[]'))); // true console.log(vm.runInNewContext('Array').isArray(vm.runInNewContext('[]'))); // true console.log(vm.runInNewContext('Array').isArray([])); // true ``` In general, using `instanceof` (or `FunctionPrototypeSymbolHasInstance`) checks is not recommended, consider checking for the presence of properties or methods for more reliable results.	23.7 KB	2025-02-28 19:16
📄 pull-requests.md # Pull requests * [Dependencies](#dependencies) * [Setting up your local environment](#setting-up-your-local-environment) * [Step 1: Fork](#step-1-fork) * [Step 2: Branch](#step-2-branch) * [The process of making changes](#the-process-of-making-changes) * [Step 3: Code](#step-3-code) * [Step 4: Commit](#step-4-commit) * [Commit message guidelines](#commit-message-guidelines) * [Step 5: Rebase](#step-5-rebase) * [Step 6: Test](#step-6-test) * [Step 7: Push](#step-7-push) * [Step 8: Opening the pull request](#step-8-opening-the-pull-request) * [Step 9: Discuss and update](#step-9-discuss-and-update) * [Approval and request changes workflow](#approval-and-request-changes-workflow) * [Step 10: Landing](#step-10-landing) * [Reviewing pull requests](#reviewing-pull-requests) * [Review a bit at a time](#review-a-bit-at-a-time) * [Be aware of the person behind the code](#be-aware-of-the-person-behind-the-code) * [Respect the minimum wait time for comments](#respect-the-minimum-wait-time-for-comments) * [Abandoned or stalled pull requests](#abandoned-or-stalled-pull-requests) * [Approving a change](#approving-a-change) * [Accept that there are different opinions about what belongs in Node.js](#accept-that-there-are-different-opinions-about-what-belongs-in-nodejs) * [Performance is not everything](#performance-is-not-everything) * [Continuous integration testing](#continuous-integration-testing) * [Notes](#notes) * [Commit squashing](#commit-squashing) * [Getting approvals for your pull request](#getting-approvals-for-your-pull-request) * [Waiting until the pull request gets landed](#waiting-until-the-pull-request-gets-landed) * [Check out the collaborator guide](#check-out-the-collaborator-guide) * [Appendix: subsystems](#appendix-subsystems) ## Dependencies Node.js has several bundled dependencies in the _deps/_ and the _tools/_ directories that are not part of the project proper. These are detailed in the [maintaining dependencies][] document. Changes to files in those directories should be sent to their respective projects. Do not send a patch to Node.js. We cannot accept such patches. In case of doubt, open an issue in the [issue tracker](https://github.com/nodejs/node/issues/) or contact one of the [project collaborators](https://github.com/nodejs/node/#current-project-team-members). Node.js has many channels on the [OpenJS Foundation Slack](https://slack-invite.openjsf.org/). Interesting channels are: [#nodejs](https://openjs-foundation.slack.com/archives/CK9Q4MB53) for general help, questions, and discussions. [#nodejs-core](https://openjs-foundation.slack.com/archives/C019Y2T6STH) for development of Node.js core specifically. Node.js also has an unofficial IRC channel: [#Node.js](https://web.libera.chat/?channels=node.js). ## Setting up your local environment To get started, you will need to have `git` installed locally. Depending on your operating system, there are also a number of other dependencies required. These are detailed in the [Building guide][]. Depending on your environment you might want to grab IDE specific settings from [IDE configs](https://github.com/nodejs/node-code-ide-configs). Once you have `git` and are sure you have all of the necessary dependencies, it's time to create a fork. ### Step 1: Fork Fork the project [on GitHub](https://github.com/nodejs/node) and clone your fork locally. ```bash git clone git@github.com:username/node.git cd node git remote add upstream https://github.com/nodejs/node.git git fetch upstream ``` Configure `git` so that it knows who you are: ```bash git config user.name "J. Random User" git config user.email "j.random.user@example.com" ``` You can use any name/email address you prefer here. We only use the metadata generated by `git` using this configuration for properly attributing your changes to you in the `AUTHORS` file and the changelog. If you would like for the GitHub UI to link the commit to your account and award you the `Contributor` label after the changes have been merged, make sure this local email is also added to your [GitHub email list](https://github.com/settings/emails). ### Step 2: Branch As a best practice to keep your development environment as organized as possible, create local branches to work within. These should also be created directly off of the upstream default branch. ```bash git checkout -b my-branch -t upstream/HEAD ``` ## The process of making changes ### Step 3: Code Pull requests in Node.js typically involve changes to one or more of a few places in the repository. * C/C++ code contained in the `src` directory * JavaScript code contained in the `lib` directory * Documentation in `doc/api` * Tests within the `test` directory If you are modifying code, please be sure to run `make lint` (or `vcbuild.bat lint` on Windows) to ensure that the changes follow the Node.js code style guide. Any documentation you write (including code comments and API documentation) should follow the [Style Guide](../../doc/README.md). Code samples included in the API docs will also be checked when running `make lint` (or `vcbuild.bat lint` on Windows). If you are adding to or deprecating an API, add or change the appropriate YAML documentation. Use `REPLACEME` for the version number in the documentation YAML: ```markdown ### `request.method` <!-- YAML added: REPLACEME --> * {string} The request method. ``` For contributing C++ code, you may want to look at the [C++ Style Guide](cpp-style-guide.md), as well as the [README of `src/`](../../src/README.md) for an overview of Node.js C++ internals. ### Step 4: Commit It is a best practice to keep your changes as logically grouped as possible within individual commits. There is no limit to the number of commits any single pull request may have, and many contributors find it easier to review changes that are split across multiple commits. ```bash git add my/changed/files git commit ``` Multiple commits often get squashed when they are landed. See the notes about [commit squashing](#commit-squashing). #### Commit message guidelines A good commit message should describe what changed and why. 1. The first line should: * contain a short description of the change (preferably 50 characters or less, and no more than 72 characters) * be entirely in lowercase with the exception of proper nouns, acronyms, and the words that refer to code, like function/variable names * be prefixed with the name of the changed [subsystem](#appendix-subsystems) and start with an imperative verb. Check the output of `git log --oneline files/you/changed` to find out what subsystems your changes touch. Examples: * `net: add localAddress and localPort to Socket` * `src: fix typos in async_wrap.h` 2. Keep the second line blank. 3. Wrap all other lines at 72 columns (except for long URLs). 4. If your patch fixes an open issue, you can add a reference to it at the end of the log. Use the `Fixes:` prefix and the full issue URL. For other references use `Refs:`. Examples: * `Fixes: https://github.com/nodejs/node/issues/1337` * `Refs: https://eslint.org/docs/rules/space-in-parens.html` * `Refs: https://github.com/nodejs/node/pull/3615` 5. If your commit introduces a breaking change (`semver-major`), it should contain an explanation about the reason of the breaking change, which situation would trigger the breaking change, and what is the exact change. Sample complete commit message: ```text subsystem: explain the commit in one line The body of the commit message should be one or more paragraphs, explaining things in more detail. Please word-wrap to keep columns to 72 characters or less. Fixes: https://github.com/nodejs/node/issues/1337 Refs: https://eslint.org/docs/rules/space-in-parens.html ``` If you are new to contributing to Node.js, please try to do your best at conforming to these guidelines, but do not worry if you get something wrong. One of the existing contributors will help get things situated and the contributor landing the pull request will ensure that everything follows the project guidelines. ### Step 5: Rebase As a best practice, once you have committed your changes, it is a good idea to use `git rebase` (not `git merge`) to synchronize your work with the main repository. ```bash git fetch upstream HEAD git rebase FETCH_HEAD ``` This ensures that your working branch has the latest changes from `nodejs/node`. ### Step 6: Test Bug fixes and features should always come with tests. A [guide for writing tests in Node.js][] has been provided to make the process easier. Looking at other tests to see how they should be structured can also help. The `test` directory within the `nodejs/node` repository is complex and it is often not clear where a new test file should go. When in doubt, add new tests to the `test/parallel/` directory and the right location will be sorted out later. Before submitting your changes in a pull request, always run the full Node.js test suite. To run the tests (including code linting) on Unix / macOS: ```bash ./configure && make -j4 test ``` We can speed up the builds by using [Ninja](https://ninja-build.org/). For more information, see [Building Node.js with Ninja](building-node-with-ninja.md). And on Windows: ```powershell vcbuild test ``` For some configurations, running all tests might take a long time (an hour or more). To run a subset of the test suite, see the [running tests][] section of the Building guide. ### Step 7: Push Once you are sure your commits are ready to go, with passing tests and linting, begin the process of opening a pull request by pushing your working branch to your fork on GitHub. ```bash git push origin my-branch ``` ### Step 8: Opening the pull request From within GitHub, opening a new pull request will present you with a [pull request template][]. Please try to do your best at filling out the details, but feel free to skip parts if you're not sure what to put. Once opened, pull requests are usually reviewed within a few days. To get feedback on your proposed change even though it is not ready to land, use the `Convert to draft` option in the GitHub UI. Do not use the `wip` label as it might not prevent the PR from landing before you are ready. ### Step 9: Discuss and update You will probably get feedback or requests for changes to your pull request. This is a big part of the submission process so don't be discouraged! Some contributors may sign off on the pull request right away, others may have more detailed comments or feedback. This is a necessary part of the process in order to evaluate whether the changes are correct and necessary. To make changes to an existing pull request, make the changes to your local branch, add a new commit with those changes, and push those to your fork. GitHub will automatically update the pull request. ```bash git add my/changed/files git commit git push origin my-branch ``` If a git conflict arises, it is necessary to synchronize your branch with other changes that have landed upstream by using `git rebase`: ```bash git fetch upstream HEAD git rebase FETCH_HEAD git push --force-with-lease origin my-branch ``` Important: The `git push --force-with-lease` command is one of the few ways to delete history in `git`. It also complicates the review process, as it won't allow reviewers to get a quick glance on what changed. Before you use it, make sure you understand the risks. If in doubt, you can always ask for guidance in the pull request. There are a number of more advanced mechanisms for managing commits using `git rebase` that can be used, but are beyond the scope of this guide. Feel free to post a comment in the pull request to ping reviewers if you are awaiting an answer on something. If you encounter words or acronyms that seem unfamiliar, refer to this [glossary](https://github.com/nodejs/node/blob/HEAD/glossary.md). #### Approval and request changes workflow All pull requests require "sign off" in order to land. Whenever a contributor reviews a pull request they may find specific details that they would like to see changed or fixed. These may be as simple as fixing a typo, or may involve substantive changes to the code you have written. While such requests are intended to be helpful, they may come across as abrupt or unhelpful, especially requests to change things that do not include concrete suggestions on _how_ to change them. Try not to be discouraged. If you feel that a particular review is unfair, say so, or contact one of the other contributors in the project and seek their input. Often such comments are the result of the reviewer having only taken a short amount of time to review and are not ill-intended. Such issues can often be resolved with a bit of patience. That said, reviewers should be expected to be helpful in their feedback, and feedback that is simply vague, dismissive, and unhelpful is likely safe to ignore. ### Step 10: Landing In order to land, a pull request needs to be reviewed and [approved][] by at least two Node.js Collaborators (one collaborator approval is enough if the pull request has been open for more than 7 days) and pass a [CI (Continuous Integration) test run][]. After that, as long as there are no objections from other contributors, the pull request can be merged. If you find your pull request waiting longer than you expect, see the [notes about the waiting time](#waiting-until-the-pull-request-gets-landed). When a collaborator lands your pull request, they will post a comment to the pull request page mentioning the commit(s) it landed as. GitHub might show the pull request as `Closed` at this point, but don't worry. If you look at the branch you raised your pull request against, you should see a commit with your name on it. Congratulations and thanks for your contribution! ## Reviewing pull requests All Node.js contributors who choose to review and provide feedback on Pull Requests have a responsibility to both the project and the individual making the contribution. Reviews and feedback must be helpful, insightful, and geared towards improving the contribution as opposed to simply blocking it. Do not expect to be able to block a pull request from advancing simply because you say "No" without giving an explanation. Be open to having your mind changed. Be open to working with the contributor to make the pull request better. Reviews that are dismissive or disrespectful of the contributor or any other reviewers are strictly counter to the [Code of Conduct][]. When reviewing a pull request, the primary goals are for the codebase to improve and for the person submitting the request to succeed. Even if a pull request does not land, the submitters should come away from the experience feeling like their effort was not wasted or unappreciated. Every pull request from a new contributor is an opportunity to grow the community. ### Review a bit at a time Do not overwhelm new contributors. It is tempting to micro-optimize and make everything about relative performance, perfect grammar, or exact style matches. Do not succumb to that temptation. Focus first on the most significant aspects of the change: 1. Does this change make sense for Node.js? 2. Does this change make Node.js better, even if only incrementally? 3. Are there clear bugs or larger scale issues that need attending to? 4. Is the commit message readable and correct? If it contains a breaking change is it clear enough? When changes are necessary, _request_ them, do not _demand_ them, and do not assume that the submitter already knows how to add a test or run a benchmark. Specific performance optimization techniques, coding styles, and conventions change over time. The first impression you give to a new contributor never does. Nits (requests for small changes that are not essential) are fine, but try to avoid stalling the pull request. Most nits can typically be fixed by the Node.js collaborator landing the pull request but they can also be an opportunity for the contributor to learn a bit more about the project. It is always good to clearly indicate nits when you comment: e.g. `Nit: change foo() to bar(). But this is not blocking.` If your comments were addressed but were not folded automatically after new commits or if they proved to be mistaken, please, [hide them][hiding-a-comment] with the appropriate reason to keep the conversation flow concise and relevant. ### Be aware of the person behind the code Be aware that _how_ you communicate requests and reviews in your feedback can have a significant impact on the success of the pull request. Yes, we may land a particular change that makes Node.js better, but the individual might just not want to have anything to do with Node.js ever again. The goal is not just having good code. ### Respect the minimum wait time for comments There is a minimum waiting time which we try to respect for non-trivial changes, so that people who may have important input in such a distributed project are able to respond. For non-trivial changes, pull requests must be left open for at least 48 hours. Sometimes changes take far longer to review, or need more specialized review from subject-matter experts. When in doubt, do not rush. Trivial changes, typically limited to small formatting changes or fixes to documentation, may be landed within the minimum 48 hour window. ### Abandoned or stalled pull requests If a pull request appears to be abandoned or stalled, it is polite to first check with the contributor to see if they intend to continue the work before checking if they would mind if you took it over (especially if it just has nits left). When doing so, it is courteous to give the original contributor credit for the work they started (either by preserving their name and email address) in the commit log, or by using an `Author:` meta-data tag in the commit. ### Approving a change Any Node.js core collaborator (any GitHub user with commit rights in the `nodejs/node` repository) is authorized to approve any other contributor's work. Collaborators are not permitted to approve their own pull requests. Collaborators indicate that they have reviewed and approve of the changes in a pull request either by using GitHub's Approval Workflow, which is preferred, or by leaving an `LGTM` ("Looks Good To Me") comment. When explicitly using the "Changes requested" component of the GitHub Approval Workflow, show empathy. That is, do not be rude or abrupt with your feedback and offer concrete suggestions for improvement, if possible. If you're not sure _how_ a particular change can be improved, say so. Most importantly, after leaving such requests, it is courteous to make yourself available later to check whether your comments have been addressed. If you see that requested changes have been made, you can clear another collaborator's `Changes requested` review. Change requests that are vague, dismissive, or unconstructive may also be dismissed if requests for greater clarification go unanswered within a reasonable period of time. Use `Changes requested` to block a pull request from landing. When doing so, explain why you believe the pull request should not land along with an explanation of what may be an acceptable alternative course, if any. ### Accept that there are different opinions about what belongs in Node.js Opinions on this vary, even among the members of the Technical Steering Committee. One general rule of thumb is that if Node.js itself needs it (due to historic or functional reasons), then it belongs in Node.js. For instance, `url` parsing is in Node.js because of HTTP protocol support. Also, functionality that either cannot be implemented outside of core in any reasonable way, or only with significant pain. It is not uncommon for contributors to suggest new features they feel would make Node.js better. These may or may not make sense to add, but as with all changes, be courteous in how you communicate your stance on these. Comments that make the contributor feel like they should have "known better" or ridiculed for even trying run counter to the [Code of Conduct][]. ### Performance is not everything Node.js has always optimized for speed of execution. If a particular change can be shown to make some part of Node.js faster, it's quite likely to be accepted. Claims that a particular pull request will make things faster will almost always be met by requests for performance [benchmark results][] that demonstrate the improvement. That said, performance is not the only factor to consider. Node.js also optimizes in favor of not breaking existing code in the ecosystem, and not changing working functional code just for the sake of changing. If a particular pull request introduces a performance or functional regression, rather than simply rejecting the pull request, take the time to work _with_ the contributor on improving the change. Offer feedback and advice on what would make the pull request acceptable, and do not assume that the contributor should already know how to do that. Be explicit in your feedback. ### Continuous integration testing All pull requests that contain changes to code must be run through continuous integration (CI) testing at [https://ci.nodejs.org/][]. Only Node.js core collaborators and triagers can start a CI testing run. The specific details of how to do this are included in the new collaborator [Onboarding guide][]. Usually, a collaborator or triager will start a CI test run for you as approvals for the pull request come in. If not, you can ask a collaborator or triager to start a CI run. Ideally, the code change will pass ("be green") on all platform configurations supported by Node.js. This means that all tests pass and there are no linting errors. In reality, however, it is not uncommon for the CI infrastructure itself to fail on specific platforms or for so-called "flaky" tests to fail ("be red"). It is vital to visually inspect the results of all failed ("red") tests to determine whether the failure was caused by the changes in the pull request. ## Notes ### Commit squashing In most cases, do not squash commits that you add to your pull request during the review process. When the commits in your pull request land, they may be squashed into one commit per logical change. Metadata will be added to the commit message (including links to the pull request, links to relevant issues, and the names of the reviewers). The commit history of your pull request, however, will stay intact on the pull request page. For the size of "one logical change", [0b5191f](https://github.com/nodejs/node/commit/0b5191f15d0f311c804d542b67e2e922d98834f8) can be a good example. It touches the implementation, the documentation, and the tests, but is still one logical change. All tests should always pass when each individual commit lands on one of the `nodejs/node` branches. ### Getting approvals for your pull request A pull request is approved either by saying LGTM, which stands for "Looks Good To Me", or by using GitHub's Approve button. GitHub's pull request review feature can be used during the process. For more information, check out [the official documentation](https://help.github.com/articles/reviewing-changes-in-pull-requests/). After you push new changes to your branch, you need to get approval for these new changes again, even if GitHub shows "Approved" because the reviewers have hit the buttons before. ### Waiting until the pull request gets landed A pull request needs to stay open for at least 48 hours from when it is submitted, even after it gets approved and passes the CI. This is to make sure that everyone has a chance to weigh in. If the changes are trivial, collaborators may decide it doesn't need to wait. A pull request may well take longer to be merged in. All these precautions are important because Node.js is widely used, so don't be discouraged! ### Check out the collaborator guide If you want to know more about the code review and the landing process, see the [collaborator guide][]. ### Appendix: subsystems * `lib/.js` (`assert`, `buffer`, etc.) `build` * `doc` * `lib / src` * `test` * `tools` You can find the full list of supported subsystems in the [nodejs/core-validate-commit][] repository. More than one subsystem may be valid for any particular issue or pull request. [Building guide]: ../../BUILDING.md [CI (Continuous Integration) test run]: #continuous-integration-testing [Code of Conduct]: https://github.com/nodejs/admin/blob/HEAD/CODE_OF_CONDUCT.md [Onboarding guide]: ../../onboarding.md [approved]: #getting-approvals-for-your-pull-request [benchmark results]: writing-and-running-benchmarks.md [collaborator guide]: collaborator-guide.md [guide for writing tests in Node.js]: writing-tests.md [hiding-a-comment]: https://help.github.com/articles/managing-disruptive-comments/#hiding-a-comment [https://ci.nodejs.org/]: https://ci.nodejs.org/ [maintaining dependencies]: ./maintaining/maintaining-dependencies.md [nodejs/core-validate-commit]: https://github.com/nodejs/core-validate-commit/blob/main/lib/rules/subsystem.js [pull request template]: https://raw.githubusercontent.com/nodejs/node/HEAD/.github/PULL_REQUEST_TEMPLATE.md [running tests]: ../../BUILDING.md#running-tests	24.81 KB	2025-02-28 19:16
📄 recognizing-contributors.md # Recognizing Contributors The project looks to recognize and thank contributors for their contributions as one of the ways we can help them continue to contribute to the project. This document captures some of the processes we have in place to do that. Some of the benefits we hope to achieve through these programs include: * Ensuring people know that the project appreciates their work * Encouraging people to repeat/grow their contributions * Helping people demonstrate to their managers the value of the contributions they are making, which in terms helps their manager support their employer investing in the project (unfortunately this is something that matters) * Highlighting the new features in Node.js and showing that they are being added by individuals like those mentioned. This should encourage other people to get involved and make similar contributions. * Highlighting those leading efforts/initiatives and they are being done by individuals or teams like those mentioned. This should encourage other people to get involved and make similar contributions ## Sponsorship link on nodejs/node README.md Collaborators may add a single link beside their name on the nodejs/node [`README.md`](../../README.md) file in the section titled `Collaborators` named `Support me`. This link may be: 1. a direct link to one of the sponsorship platforms listed below, 2. a page that has text explaining how to support the collaborator including zero or more links to the sponsorship platforms listed below. The page should not have any outgoing links other than to the sponsorship platforms. We expect and trust collaborators to ensure that the text is professional and respectful. The sponsorship platforms to which links can be made currently includes (in alphabetical order): * [GitHub Sponsors](https://github.com/sponsors) * [Polar](https://polar.sh/) * [thanks.dev](https://thanks.dev) ## Amplification of posts announcing talks by collaborators When a collaborator is speaking at a public event they may request amplification by the Node.js social media accounts. They can request that a post highlighting that they are speaking at the event be amplified by the Node.js accounts by making a request in the #nodejs-social channel in the OpenJS Foundation slack. We trust that collaborators will only request amplification when they believe the event is relevant to the Node.js community and the content of the post is in line with the norms of the project. ## Bi-monthly contributor spotlight The contributor spotlight program showcases individual(s) or teams who have made signification contributions to the project. Anybody who is not a member of the Technical Steering Committee (TSC) and has made a notable contribution to the project can be nominated. They DO NOT need to be a collaborator, team member etc. The work of the team or individual(s) will be showcased on the Node.js social channels and, if warranted, through a blog post created by the OpenJS marketing staff along with the team or individual(s) which will be published on [openjsf.org](https://openjsf.org/). Nominations can be made through this web form: [Contributor Spotlight nomination](https://forms.gle/dXBXZn8yu83HLJ57A) Nominations will be reviewed/approved by the Technical Steering Committee (TSC) on a regular basis as scheduled by the TSC chair. The TSC will also recommend the order in which approved nominations are processed by the OpenJS marketing staff. Before any work proceeds on an approved nomination the individual(s) or team will be contacted to confirm they want to participate. Social content and or spotlight blog post will only be published after the team or individual(s) have confirmed they are happy with the content.	3.68 KB	2025-02-28 19:16
📄 releases-node-api.md # Node.js Node-API version release process This document describes the technical aspects of the Node.js Node-API version release process. ## Table of contents * [How to create a release](#how-to-create-a-release) * [0. Pre-release steps](#0-pre-release-steps) * [1. Update the main branch](#1-update-the-main-branch) * [2. Create a new branch for the release](#2-create-a-new-branch-for-the-release) * [3. Update `NODE_API_SUPPORTED_VERSION_MAX`](#3-update-node_api_supported_version_max) * [4. Define `addon_context_register_func`](#4-define-addon_context_register_func) * [5. Update version guards](#5-update-version-guards) * [6. Create release commit](#6-create-release-commit) * [7. Propose release on GitHub](#7-propose-release-on-github) * [8. Ensure that the release branch is stable](#8-ensure-that-the-release-branch-is-stable) * [9. Land the release](#9-land-the-release) * [10. Backport the release](#10-backport-the-release) ## How to create a release Notes: * Version strings are listed below as _"vx"_ or _"x"_. Substitute for the release version. * Examples will use the integer release version `10`. ### 0. Pre-release steps Before preparing a Node.js Node-API version release, the Node-API Working Group must be notified at least one business day in advance of the expected release. Node-API Working Group can be contacted best by opening up an issue on the [abi-stable-node issue tracker][]. ### 1. Update the main Branch Checkout the staging branch locally. ```bash git remote update git checkout main git reset --hard upstream/main ``` If the staging branch is not up to date relative to `main`, bring the appropriate PRs and commits into it. ### 2. Create a new branch for the release Create a new branch named `node-api-x-proposal`, off the main branch. ```bash git checkout -b node-api-10-proposal upstream/main ``` ### 3. Update `NODE_API_SUPPORTED_VERSION_MAX` Set the version for the proposed release using the following macros, which are already defined in `src/node_version.h`: ```c #define NODE_API_SUPPORTED_VERSION_MAX x ``` > Note: Do not update the `NAPI_VERSION` defined in `src/js_native_api.h`. It > is a fixed constant baseline version of Node-API. ### 4. Define `addon_context_register_func` For each new version of Node-API an `else if` case must be added to `get_node_api_context_register_func` in `src/node_api.cc` and the numeric literal used in the `static_assert` statement in that function must be updated to the new Node-API version. ### 5. Update version guards #### Step 1. Update define version guards If this release includes new Node-APIs that were first released in this version, the relevant commits should already include the `NAPI_EXPERIMENTAL` define guards on the declaration of the new Node-API. Check for these guards with: ```bash grep \ -E \ 'N(ODE_)?API_EXPERIMENTAL' \ src/js_native_api{_types,}.h \ src/node_api{_types,}.h ``` and update the define version guards with the release version: ```diff - #ifdef NAPI_EXPERIMENTAL + #if NAPI_VERSION >= 10 NAPI_EXTERN napi_status NAPI_CDECL node_api_function(napi_env env); - #endif // NAPI_EXPERIMENTAL + #endif // NAPI_VERSION >= 10 ``` Remove any feature flags of the form `NODE_API_EXPERIMENTAL_HAS_<FEATURE>`. Remove any additional `NODE_API_EXPERIMENTAL_` guards along with `NAPI_EXPERIMENTAL`. Also, update the Node-API version value of the `napi_get_version` test in `test/js-native-api/test_general/test.js` with the release version `x`: ```diff // Test version management functions - assert.strictEqual(test_general.testGetVersion(), 9); + assert.strictEqual(test_general.testGetVersion(), 10); ``` #### Step 2. Update runtime version guards If this release includes runtime behavior version guards, the relevant commits should already include `NAPI_VERSION_EXPERIMENTAL` guard for the change. Check for these guards with: ```bash grep NAPI_VERSION_EXPERIMENTAL src/js_native_api_v8 src/node_api.cc ``` and substitute this guard version with the release version `x`. #### Step 3. Update test version guards If this release includes add-on tests for the new Node-APIs, the relevant commits should already include `NAPI_EXPERIMENTAL` definition for the tests. Check for these definitions with: ```bash grep \ -E \ 'N(ODE_)?API_EXPERIMENTAL' \ test/node-api//{.{h,c},binding.gyp} \ test/js-native-api//{.{h,c},binding.gyp} ``` and substitute the `NAPI_EXPERIMENTAL` with the release version `NAPI_VERSION x`; ```diff - #define NAPI_EXPERIMENTAL + #define NAPI_VERSION 10 ``` Remove any `NODE_API_EXPERIMENTAL_` flags. #### Step 4. Update document If this release includes new Node-APIs that were first released in this version and are necessary to document, the relevant commits should already have documented the new Node-API. For all Node-API functions and types with define guards updated in Step 1, in `doc/api/n-api.md`, add the `napiVersion: x` metadata to the Node-API types and functions that are released in the version, and remove the experimental stability banner: ```diff #### node_api_function <!-- YAML added: - v1.2.3 + napiVersion: 10 --> - > Stability: 1 - Experimental ``` #### Step 5. Update change history If this release includes new Node-APIs runtime version guards that were first released in this version and are necessary to document, the relevant commits should already have documented the new behavior in a "Change History" section. For all runtime version guards updated in Step 2, check for these definitions with: ```bash grep NAPI_EXPERIMENTAL doc/api/n-api.md ``` In `doc/api/n-api.md`, update the `experimental` change history item to be the released version `x`: ```diff Change History: - experimental (`NAPI_EXPERIMENTAL` is defined): + * version 10: ``` ### 6. Create release commit When committing these to git, use the following message format: ```text node-api: define version x ``` ### 7. Propose release on GitHub Create a pull request targeting the `main` branch. These PRs should be left open for at least 24 hours, and can be updated as new commits land. If you need any additional information about any of the commits, this PR is a good place to @-mention the relevant contributors. Tag the PR with the `notable-change` label, and @-mention the GitHub team @nodejs/node-api and @nodejs/node-api-implementer. ### 8. Ensure that the release branch is stable Run a [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) test run to ensure that the build is stable and the HEAD commit is ready for release. ### 9. Land the release See the steps documented in [Collaborator Guide - Landing a PR][] to land the PR. ### 10. Backport the release Consider backporting the release to all LTS versions following the steps documented in the [backporting guide][]. [Collaborator Guide - Landing a PR]: ./collaborator-guide.md#landing-pull-requests [abi-stable-node issue tracker]: https://github.com/nodejs/abi-stable-node/issues [backporting guide]: backporting-to-release-lines.md	7.06 KB	2025-02-28 19:16
📄 releases.md # Node.js release process This document describes the technical aspects of the Node.js release process. The intended audience is those who have been authorized by the Node.js Technical Steering Committee (TSC) to create, promote, and sign official release builds for Node.js, hosted on <https://nodejs.org/>. ## Table of contents * [Who can make a release?](#who-can-make-a-release) * [1. Jenkins release access](#1-jenkins-release-access) * [2. \<nodejs.org> access](#2-nodejsorg-access) * [3. A publicly listed GPG key](#3-a-publicly-listed-gpg-key) * [How to create a release](#how-to-create-a-release) * [0. Pre-release steps](#0-pre-release-steps) * [1. Update the staging branch](#1-update-the-staging-branch) * [2. Create a new branch for the release](#2-create-a-new-branch-for-the-release) * [3. Update `src/node_version.h`](#3-update-srcnode_versionh) * [4. Update the changelog](#4-update-the-changelog) * [5. Create release commit](#5-create-release-commit) * [6. Propose release on GitHub](#6-propose-release-on-github) * [7. Ensure that the release branch is stable](#7-ensure-that-the-release-branch-is-stable) * [7.1 Updating the release _(optional)_](#71-updating-the-release-optional) * [8. Produce a nightly build _(optional)_](#8-produce-a-nightly-build-optional) * [9. Produce release builds](#9-produce-release-builds) * [10. Test the build](#10-test-the-build) * [11. Tag and sign the release commit](#11-tag-and-sign-the-release-commit) * [12. Set up for the next release](#12-set-up-for-the-next-release) * [13. Cherry-pick the release commit to `main`](#13-cherry-pick-the-release-commit-to-main) * [14. Push the release tag](#14-push-the-release-tag) * [15. Promote and sign the release builds](#15-promote-and-sign-the-release-builds) * [16. Check the release](#16-check-the-release) * [17. Create a blog post](#17-create-a-blog-post) * [18. Create the release on GitHub](#18-create-the-release-on-github) * [19. Announce](#19-announce) * [20. Celebrate](#20-celebrate) * [LTS releases](#lts-releases) * [Major releases](#major-releases) ## Who can make a release? Release authorization is given by the Node.js TSC. Once authorized, an individual must have the following: ### 1. Jenkins release access There are three relevant Jenkins jobs that should be used for a release flow: a. Test runs: [node-test-pull-request](https://ci.nodejs.org/job/node-test-pull-request/) is used for a final full-test run to ensure that the current _HEAD_ is stable. b. Nightly builds: (optional) [iojs+release](https://ci-release.nodejs.org/job/iojs+release/) can be used to create a nightly release for the current _HEAD_ if public test releases are required. Builds triggered with this job are published straight to <https://nodejs.org/download/nightly/> and are available for public download. c. Release builds: [iojs+release](https://ci-release.nodejs.org/job/iojs+release/) does all of the work to build all required release assets. Promotion of the release files is a manual step once they are ready (see below). The [Node.js build team](https://github.com/nodejs/build) is able to provide this access to individuals authorized by the TSC. ### 2. \<nodejs.org> access The _dist_ user on nodejs.org controls the assets available in <https://nodejs.org/download/>. <https://nodejs.org/dist/> is an alias for <https://nodejs.org/download/release/>. The Jenkins release build workers upload their artifacts to the web server as the _staging_ user. The _dist_ user has access to move these assets to public access while, for security, the _staging_ user does not. Nightly builds are promoted automatically on the server by a cron task for the _dist_ user. Release builds require manual promotion by an individual with SSH access to the server as the _dist_ user. The [Node.js build team](https://github.com/nodejs/build) is able to provide this access to individuals authorized by the TSC. ### 3. A publicly-listed GPG key A `SHASUMS256.txt` file is produced for every promoted build, nightly, and releases. Additionally for releases, this file is signed by the individual responsible for that release. In order to be able to verify downloaded binaries, the public should be able to check that the `SHASUMS256.txt` file has been signed by someone who has been authorized to create a release. The public keys should be fetchable from a known third-party keyserver. The OpenPGP keyserver at <https://keys.openpgp.org/> is recommended. Use the [submission](https://keys.openpgp.org/upload) form to submit a new public key, and make sure to verify the associated email. You'll need to do an ASCII-armored export of your key first: ```bash gpg --armor --export email@server.com > ~/nodekey.asc ``` Keys should be fetchable via: ```bash gpg --keyserver hkps://keys.openpgp.org --recv-keys <FINGERPRINT> ``` The key you use may be a child/subkey of an existing key. Additionally, full GPG key fingerprints for individuals authorized to release should be listed in the Node.js GitHub README.md file. ## How to create a release Notes: * Dates listed below as _"YYYY-MM-DD"_ should be the date of the release as UTC. Use `date -u +'%Y-%m-%d'` to find out what this is. * Version strings are listed below as _"vx.y.z"_ or _"x.y.z"_. Substitute for the release version. * Examples will use the fictional release version `1.2.3`. * When preparing a security release, follow the security steps in the details sections. ### 0. Pre-release steps Before preparing a Node.js release, the Build Working Group must be notified at least one business day in advance of the expected release. Coordinating with Build is essential to make sure that the CI works, release files are published, and the release blog post is available on the project website. Build can be contacted best by opening up an issue on the [Build issue tracker][]. When preparing a security release, contact Build at least two weekdays in advance of the expected release. To ensure that the security patch(es) can be properly tested, run a `node-test-pull-request` job against the `main` branch of the `nodejs-private/node-private` repository a day or so before the [CI lockdown procedure][] begins. This is to confirm that Jenkins can properly access the private repository. ### 1. Update the staging branch Checkout the staging branch locally. ```bash git remote update git checkout v1.x-staging git reset --hard upstream/v1.x-staging ``` If the staging branch is not up to date relative to `main`, bring the appropriate PRs and commits into it. Go through PRs with the label `vN.x`. e.g. [PRs with the `v8.x` label](https://github.com/nodejs/node/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3Av8.x) and `baking-for-lts` label if preparing a release for an LTS line. For each PR: * Run or check that there is a passing CI. * Check approvals (you can approve yourself). * Check that the commit metadata was not changed from the `main` commit. * If there are merge conflicts, ask the PR author to rebase. Simple conflicts can be resolved when landing. * If `baking-for-lts` is present, check if the PR is ready to be landed. If it is, remove the `baking-for-lts` label. When landing the PR add the `Backport-PR-URL:` line to each commit. Close the backport PR with `Landed in ...`. Update the label on the original PR from `backport-requested-vN.x` to `backported-to-vN.x`. You can add the `Backport-PR-URL` metadata by using `--backport` with `git node land` ```bash git node land --backport $PR-NUMBER ``` To determine the relevant commits, use [`branch-diff`](https://github.com/nodejs/branch-diff). The tool is available on npm and should be installed globally or run with `npx`. It depends on our commit metadata, as well as the GitHub labels such as `semver-minor` and `semver-major`. One drawback is that when the `PR-URL` metadata is accidentally omitted from a commit, the commit will show up because it's unsure if it's a duplicate or not. For a list of commits that could be landed in a minor release on v1.x: ```bash N=1 sh -c 'branch-diff v$N.x-staging upstream/main --exclude-label=semver-major,dont-land-on-v$N.x,backport-requested-v$N.x,backport-blocked-v$N.x,backport-open-v$N.x,backported-to-v$N.x --filter-release --format=simple' ``` If the target branch is an LTS line, you should also exclude the `baking-for-lts`: ```bash N=1 sh -c 'branch-diff v$N.x-staging upstream/main --exclude-label=semver-major,dont-land-on-v$N.x,backport-requested-v$N.x,backport-blocked-v$N.x,backport-open-v$N.x,backported-to-v$N.x,baking-for-lts --filter-release --format=simple' ``` Previously released commits and version bumps do not need to be cherry-picked. Carefully review the list of commits: * Checking for errors (incorrect `PR-URL`) * Checking semver status - Commits labeled as `semver-minor` or `semver-major` should only be cherry-picked when appropriate for the type of release being made. * If you think it's risky and the change should wait for a while, add the `baking-for-lts` tag. When you are ready to cherry-pick commits, you can automate with the following command. ```bash N=1 sh -c 'branch-diff v$N.x-staging upstream/main --exclude-label=semver-major,dont-land-on-v$N.x,backport-requested-v$N.x,backport-blocked-v$N.x,backport-open-v$N.x,backported-to-v$N.x --filter-release --format=sha --reverse' \| xargs git cherry-pick -S ``` If the target branch is an LTS line, you should also exclude the `baking-for-lts`: ```bash N=1 sh -c 'branch-diff v$N.x-staging upstream/main --exclude-label=semver-major,dont-land-on-v$N.x,backport-requested-v$N.x,backport-blocked-v$N.x,backport-open-v$N.x,backported-to-v$N.x,baking-for-lts --filter-release --format=sha --reverse' \| xargs git cherry-pick -S ``` <sup>For patch releases, make sure to add the `semver-minor` tag to `exclude-label`<sup> When cherry-picking commits, if there are simple conflicts you can resolve them. Otherwise, add the `backport-requested-vN.x` label to the original PR and post a comment stating that it does not land cleanly and will require a backport PR. You can refer the owner of the PR to the "[Backporting to Release Lines](https://github.com/nodejs/node/blob/HEAD/doc/contributing/backporting-to-release-lines.md)" guide. If commits were cherry-picked in this step, check that the test still pass. ```bash make test ``` Then, push to the staging branch to keep it up-to-date. ```bash git push upstream v1.x-staging ``` <details> <summary>Security release</summary> Security releases with private patches need to be prepared in the `nodejs-private` GitHub organization. Add the `nodejs-private` remote: ```bash git remote add private git@github.com:nodejs-private/node-private.git ``` For security releases, we generally try to only include the security patches. As there may already be commits on the `vN.x-staging` branch, it is preferable to checkout the `vN.x` branch and build up the release directly in a proposal branch. ```console $ git checkout vN.x $ git reset --hard upstream/vN.x ``` The list of patches to include should be listed in the "Next Security Release" issue in `nodejs-private`. Ask the security release steward if you're unsure. The `git node land` tool does not work with the `nodejs-private` organization. To land a PR in Node.js private, use `git cherry-pick` to apply each commit from the PR. You will also need to manually apply the PR metadata (`PR-URL`, `Reviewed-by`, etc.) by amending the commit messages. If known, additionally include `CVE-ID: CVE-XXXX-XXXXX` in the commit metadata. Note: Do not run CI on the PRs in `nodejs-private` until CI is locked down. You can integrate the PRs into the proposal without running full CI. </details> ### 2. Create a new branch for the release > \[!TIP] Once the staging branch is up-to-date you can use the > [`create-release-proposal`][] action to generate the proposal. ```bash gh workflow run "Create Release Proposal" -f release-line=N -f release-date=YYYY-MM-DD ``` If you prefer to run it locally you can either run `git node release --prepare`: ```bash git node release -S --prepare x.y.z ``` to automate the remaining steps until step 6 or you can perform it manually following the below steps. *** Create a new branch named `vx.y.z-proposal`, off the corresponding staging branch. ```bash git checkout -b v1.2.3-proposal upstream/v1.x-staging ``` <details> <summary>Security release</summary> When performing Security Releases, the `vN.x.x-proposal` branch should be branched off of `vN.x`. ```console $ git checkout -b v1.2.3-proposal upstream/v1.x git cherry-pick ... # cherry-pick nodejs-private PR commits directly into the proposal ``` Be sure to label the CVE fixes as `notable-change` in the nodejs-private repository. This will ensure they are included in the "Notable Changes" section of the CHANGELOG. </details> ### 3. Update `src/node_version.h` Set the version for the proposed release using the following macros, which are already defined in `src/node_version.h`: ```c #define NODE_MAJOR_VERSION x #define NODE_MINOR_VERSION y #define NODE_PATCH_VERSION z ``` Set the `NODE_VERSION_IS_RELEASE` macro value to `1`. This causes the build to be produced with a version string that does not have a trailing pre-release tag: ```c #define NODE_VERSION_IS_RELEASE 1 ``` ### 4. Update the changelog #### Step 1: Collect the formatted list of changes Collect a formatted list of commits since the last release. Use [`changelog-maker`](https://github.com/nodejs/changelog-maker) to do this: ```bash changelog-maker --group --markdown ``` `changelog-maker` counts commits since the last tag and if the last tag in the repository was not on the current branch you may have to supply a `--start-ref` argument: ```bash changelog-maker --group --markdown --filter-release --start-ref v1.2.2 ``` `--filter-release` will remove the release commit from the previous release. #### Step 2: Update the appropriate doc/changelogs/CHANGELOG\_\.md file There is a separate `CHANGELOG_Vx.md` file for each major Node.js release line. These are located in the `doc/changelogs/` directory. Once the formatted list of changes is collected, it must be added to the top of the relevant changelog file in the release branch (e.g. a release for Node.js v4 would be added to the `/doc/changelogs/CHANGELOG_V4.md`). Please do _not_ add the changelog entries to the root `CHANGELOG.md` file.* The new entry should take the following form: ```markdown <a id="x.y.x"></a> ## YYYY-MM-DD, Version x.y.z (Release Type), @releaser ### Notable changes * List notable changes here * ... ### Commits * Include the full list of commits since the last release here. Do not include "Working on X.Y.Z+1" commits. ``` The release type should be either Current, LTS, or Maintenance, depending on the type of release being produced. By default, the `### Notable changes` section should be populated with the commits in the release that have either the `notable-change` or `semver-minor` label. Some `semver-minor` features may be determined by the releaser, or indicated by another contributor, to not be appropriate to be listed as a notable. The ultimate decision rests with the releaser. You can use `branch-diff` to get a list of commits with the `notable-change` label: ```bash branch-diff upstream/v1.x v1.2.3-proposal --require-label=notable-change --plaintext ``` Be sure that the `<a>` tag, as well as the two headings, are not indented at all. <details> <summary>Security release</summary> For security releases, it is necessary to include more detailed information including which vulnerabilities have been fixed, and any revert flags or workarounds to revert to the old behavior. You can use the following template as a guide: ```markdown <a id="x.y.x"></a> ## YYYY-MM-DD, Version x.y.z (Release Type), @releaser This is a security release. ### Notable changes * <CVE Title> (High\|Medium\|Low)(CVE-XXXX-XXXXX) * ... ### Commits * Include the full list of commits since the last release here. Do not include "Working on X.Y.Z+1" commits. ``` Alternatively, refer to one of the [previous security release changelog entries](https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V17.md#2022-01-10-version-1731-current-bethgriggs) to get an idea of the structure and level of detail. For each fix, use your judgement as to whether a subheading is necessary to describe the fix in more detail. Much of this information should be able to be lifted from the "post-release" announcement (should be available in `nodejs-private`). If the CVE is being fixed in multiple release lines, try to coordinate the changelog content between the other release so the descriptions are consistent. </details> At the top of the root `CHANGELOG.md` file, there is a table indexing all releases in each major release line. A link to the new release needs to be added to it. Follow the existing examples and be sure to add the release to the _top_ of the list. The most recent release for each release line is shown in bold in the index. When updating the index, please make sure to update the display accordingly by removing the bold styling from the previous release. Run `make format-md` to ensure the `CHANGELOG_Vx.md` and `CHANGELOG.md` files are formatted correctly. #### Step 3: Update any REPLACEME and DEP00XX tags in the docs If this release includes new APIs then it is necessary to document that they were first added in this version. The relevant commits should already include `REPLACEME` tags as per the example in the [docs README](../../tools/doc/README.md). Check for these tags with ```bash grep REPLACEME doc/api/.md ``` and substitute this node version with ```bash sed -i "s/REPLACEME/$VERSION/g" doc/api/.md ``` For macOS requires the extension to be specified. ```bash sed -i "" "s/REPLACEME/$VERSION/g" doc/api/.md ``` or ```bash perl -pi -e "s/REPLACEME/$VERSION/g" doc/api/.md ``` `$VERSION` should be prefixed with a `v`. If this release includes any new deprecations it is necessary to ensure that those are assigned a proper static deprecation code. These are listed in the docs (see `doc/api/deprecations.md`) and in the source as `DEP00XX`. The code must be assigned a number (e.g. `DEP0012`). This assignment should occur when the PR is landed, but a check will be made when the release build is run. ### 5. Create release commit The `CHANGELOG.md`, `doc/changelogs/CHANGELOG_Vx.md`, `src/node_version.h`, and `REPLACEME` changes should be the final commit that will be tagged for the release. When committing these to git, use the following message format: ```text YYYY-MM-DD, Version x.y.z (Release Type) Notable changes: * Copy the notable changes list here, reformatted for plain-text PR-URL: TBD ``` <details> <summary>Security release</summary> For security releases, begin the commit message with the phrase `This is a security release.` to allow the [distribution indexer](https://github.com/nodejs/nodejs-dist-indexer) to identify it as such: ```text YYYY-MM-DD, Version x.y.z (Release Type) This is a security release. Notable changes: * Copy the notable changes list here, reformatted for plain-text PR-URL: TBD ``` Note: Ensure to push the proposal branch to the nodejs-private repository. Otherwise, you will leak the commits before the security release. </details> ### 6. Propose release on GitHub Push the release branch to `nodejs/node`, not to your own fork. This allows release branches to more easily be passed between members of the release team if necessary. Create a pull request targeting the correct release line. For example, a `v5.3.0-proposal` PR should target `v5.x`, not `main`. Paste the CHANGELOG modifications into the body of the PR so that collaborators can see what is changing. These PRs should be left open for at least 24 hours, and can be updated as new commits land. If the CHANGELOG pasted into the pull request is long enough that it slows down the GitHub UI, consider pasting the commits into `<details>` tags or in follow up comments. If using the `<details>` tag, use the following format: ```markdown <details> <summary>Commits</summary> * Full list of commits... </details> ``` If you need any additional information about any of the commits, this PR is a good place to @-mention the relevant contributors. After opening the PR, update the release commit to include `PR-URL` metadata and force-push the proposal. <details> <summary>Security release</summary> If there are private security patches, remember to push and open the proposal in the `nodejs-private` GitHub repository. </details> ### 7. Ensure that the release branch is stable Run a [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) test run to ensure that the build is stable and the HEAD commit is ready for release. Also run a [`node-test-commit-v8-linux`](https://ci.nodejs.org/job/node-test-commit-v8-linux/) test run if the release contains changes to `deps/v8`. Perform some smoke-testing. There is the [`citgm-smoker`](https://ci.nodejs.org/job/citgm-smoker/) CI job for this purpose. Run it once with the base `vx.x` branch as a reference and with the proposal branch to check if new regressions could be introduced in the ecosystem. Use `ncu-ci` to compare `vx.x` run (10) and proposal branch (11) ```bash npm i -g @node-core/utils ncu-ci citgm 10 11 ``` <details> <summary>Security release</summary> If there are private security patches, do not run any CI jobs on the proposal until CI has been locked down. The security steward should be coordinating this with the Build Working Group. </details> #### 7.1 Updating the release _(optional)_ Sometimes a release might be deferred to the subsequent day due to several conditions: * Unstable CI * Late CI completion And when it happens, the CHANGELOG\_Vx and the commit metadata needs to be updated according to the new target date. However, if it's just the changelog/commit message that has changed since the last CI execution, there's no need to rerun CI, V8, or CITGM workflows. The PR still needs a clean GitHub action run, and the original CI, V8, and CITGM run should be in a visible comment. There are some cases when a commit needs to be dropped or adjusted, consider using the following approach: 1. Update staging ```bash git checkout v1.x-staging git rebase -i $HASH_PREVIOUS_BAD_COMMIT # ... drop or edit the bad commit(s) git push -f upstream v1.x-staging ``` 2. Rebase the proposal against the updated staging branch ```bash git checkout v1.2.3-proposal git checkout -b v1.2.3-proposal-tmp git checkout v1.2.3-proposal git reset --hard upstream/v1.x-staging git cherry-pick v1.2.3-proposal-tmp ``` Note the `tmp` branch was created just to save the release commit. 3. Re-run `changelog-maker` and update the CHANGELOG\_Vx to include the new Git SHAs. Remember to update the commit message if applicable. ### 8. Produce a nightly build _(optional)_ If there is a reason to produce a test release for the purpose of having others try out installers or specifics of builds, produce a nightly build using [iojs+release](https://ci-release.nodejs.org/job/iojs+release/) and wait for it to drop in <https://nodejs.org/download/nightly/>. Follow the directions and enter a proper length commit SHA, enter a date string, and select "nightly" for "disttype". This is particularly recommended if there has been recent work relating to the macOS or Windows installers as they are not tested in any way by CI. <details> <summary>Security release</summary> Do not produce a release candidate build. </details> ### 9. Produce release builds Use [iojs+release](https://ci-release.nodejs.org/job/iojs+release/) to produce release artifacts. Enter the commit that you want to build from and select "release" for "disttype". Artifacts from each worker are uploaded to Jenkins and are available if further testing is required. Use this opportunity particularly to test macOS and Windows installers if there are any concerns. Click through to the individual workers for a run to find the artifacts. All release workers should achieve "SUCCESS" (and be green, not red). A release with failures should not be promoted as there are likely problems to be investigated. You can rebuild the release as many times as you need prior to promoting them if you encounter problems. If you have an error on Windows and need to start again, be aware that you'll get immediate failure unless you wait up to 2 minutes for the linker to stop from previous jobs. i.e. if a build fails after having started compiling, that worker will still have a linker process that's running for another couple of minutes which will prevent Jenkins from clearing the workspace to start a new one. This isn't a big deal, it's just a hassle because it'll result in another failed build if you start again! ### 10. Test the build Jenkins collects the artifacts from the builds, allowing you to download and install the new build. Make sure that the build appears correct. Check the version numbers, and perform some basic checks to confirm that all is well with the build before moving forward. Use the following list as a baseline: * `process.version` is as expected * `process.release` is as expected * `process.versions` is as expected (for example, `openssl` or `llhttp` version must be in the expected updated version) * npm version (check it matches what we expect) * Run the test suite against the built binaries (optional) * Remember to use the proposal branch * Run `make build-addons` before running the tests * Remove `config.gypi` file ```bash ./tools/test.py --shell ~/Downloads/node-v18.5.0-linux-x64/bin/node ``` ### 11. Tag and sign the release commit Once you have produced builds that you're happy with you can either run `git node release --promote` ```bash git node release -S --promote https://github.com/nodejs/node/pull/XXXX ``` to automate the remaining steps until step 16 or you can perform it manually following the below steps. * Create a new tag: By waiting until this stage to create tags, you can discard a proposed release if something goes wrong or additional commits are required. Once you have created a tag and pushed it to GitHub, you _must not_ delete and re-tag. If you make a mistake after tagging then you'll have to version-bump and start again and count that tag/version as lost. Tag summaries have a predictable format. Look at a recent tag to see: ```bash git tag -v v6.0.0 ``` The message should look something like `2016-04-26 Node.js v6.0.0 (Current) Release`. Install `git-secure-tag` npm module: ```bash npm install -g git-secure-tag ``` > Ensure to disable `--follow-tags` in your git settings using: `git config push.followTags false` If your private key is protected by a passphrase, you might need to run: ```bash export GPG_TTY=$(tty) ``` before creating the tag. To create a tag use the following command: ```bash git secure-tag <vx.y.z> <commit-sha> -sm "YYYY-MM-DD Node.js vx.y.z (<release-type>) Release" ``` <sup>The commit-sha is the release commit. You can get it easily by running `git rev-parse HEAD`</sup> `release-type` is either "Current" or "LTS". For LTS releases, you should also include the release code name. ```text 2019-10-22 Node.js v10.17.0 'Dubnium' (LTS) Release ``` The tag must be signed using the GPG key that's listed for you on the project README. Note*: Don't push the tag to remote at this point. ### 12. Set up for the next release On release proposal branch, edit `src/node_version.h` again and: Increment `NODE_PATCH_VERSION` by one * Change `NODE_VERSION_IS_RELEASE` back to `0` Commit this change with the following commit message format: ```text Working on vx.y.z # where 'z' is the incremented patch number PR-URL: <full URL to your release proposal PR> ``` This sets up the branch so that nightly builds are produced with the next version number _and_ a pre-release tag. Merge your release proposal branch into the stable branch that you are releasing from and rebase the corresponding staging branch on top of that. ```bash git checkout v1.x git merge --ff-only v1.2.3-proposal git push upstream v1.x git checkout v1.x-staging git rebase v1.x git push upstream v1.x-staging ``` <details> <summary>Security release</summary> For security releases, you can start merging the release in the `nodejs-private` GitHub organization in advance by following the same steps: ```bash git checkout v1.x git merge --ff-only v1.2.3-proposal git push private v1.x git checkout v1.x-staging git rebase v1.x git push private v1.x-staging ``` Once all releasers are ready, you can push each of the branches to the public repository. </details> ### 13. Cherry-pick the release commit to `main` ```bash git checkout main git pull upstream main git cherry-pick --strategy-option=diff-algorithm=patience v1.x^ ``` Git should stop to let you fix conflicts. Revert all changes that were made to `src/node_version.h`: ```bash git restore --source=upstream/main src/node_version.h ``` <details> <summary>Major version release</summary> On the main branch, instead of reverting changes made to `src/node_version.h` edit it instead and: * Increment `NODE_MAJOR_VERSION` by one * Reset `NODE_PATCH_VERSION` to `0` * Change `NODE_VERSION_IS_RELEASE` back to `0` Amend the current commit to apply the changes: ```bash git commit --amend ``` </details> Even if there are no conflicts, ensure that you revert all the changes that were made to `src/node_version.h`. `NODE_VERSION_IS_RELEASE` must be `0`. <sup>Edit `src/node_version.h`, revert `NODE_VERSION_IS_RELEASE` back to `0`, and `git commit --amend`</sup> If there are conflicts in `doc` due to updated `REPLACEME` placeholders (that happens when a change previously landed on another release branch), keep both version numbers. Convert the YAML field to an array if it is not already one. [It's possible that the `cherry-pick` step will end up adding and/or changing unwanted lines](https://github.com/nodejs/Release/issues/771), please validate the changes in `doc/` folder files before confirming/continuing the cherry-pick step. Then finish cherry-picking and push the commit upstream: ```bash git add src/node_version.h doc git diff --staged src doc # read output to validate that changes shows up as expected git cherry-pick --continue make lint-md && make lint-cpp git push upstream main ``` Do not cherry-pick the "Working on vx.y.z" commit to `main`. <details> <summary>Security release</summary> For security releases, you will also need to land the fixes on the `main` branch (if they apply there). Often, you can just cherry-pick the same commit that landed in the `current` security release which should already have the metadata. It is useful to first push the patches to `private/main` to check that the GitHub actions runs pass, before pushing to `upstream/main`: ```bash git checkout main git reset --hard upstream/main git cherry-pick ... # apply the patches which apply to main git push private main # push to private main first run GitHub actions git push upstream main ``` </details> ### 14. Push the release tag Push the tag to the repository before you promote the builds. If you haven't pushed your tag first, then build promotion won't work properly. Push the tag using the following command: ```bash git push upstream v1.2.3 ``` _Note_: Please do not push the tag unless you are ready to complete the remainder of the release steps. ### 15. Promote and sign the release builds The same individual who signed the release tag must be the one to promote the builds as the `SHASUMS256.txt` file needs to be signed with the same GPG key! Use `tools/release.sh` to promote and sign the build. Before doing this, you'll need to ensure you've loaded the correct ssh key, or you'll see the following: If your GPG key is protected by a password, you might need to run: ```console $ export GPG_TTY=$(tty) ``` ```console # Checking for releases ... Enter passphrase for key '/Users/<user>/.ssh/id_rsa': dist@direct.nodejs.org's password: ``` The key can be loaded either with `ssh-add`: ```bash # Substitute node_id_rsa with whatever you've named the key ssh-add ~/.ssh/node_id_rsa ``` or at runtime with: ```bash # Substitute node_id_rsa with whatever you've named the key ./tools/release.sh -i ~/.ssh/node_id_rsa ``` You can also specify a different ssh server address to connect to by defining a `NODEJS_RELEASE_HOST` environment variable: ```bash # Substitute proxy.xyz with whatever address you intend to use NODEJS_RELEASE_HOST=proxy.xyz ./tools/release.sh ``` In case `gpg` is unable to autoselect a key, you can retry using the `-a` option to enable an interactive interface: ```bash ./tools/release.sh -a ``` > \[!TIP] > Sometimes, due to machines being overloaded or other external factors, > the files at <https://nodejs.org/dist/index.json>, <https://nodejs.org/dist/index.tab> > or `SHASUMS256.txt` may not be generated correctly. > In this case you can repeat the signing step in order > to fix it. e.g: `./tools/release.sh -s`. `tools/release.sh` will perform the following actions when run: <details> a. Select a GPG key from your private keys. It will use a command similar to: `gpg --list-secret-keys` to list your keys. If you don't have any keys, it will bail. If you have only one key, it will use that. If you have more than one key it will ask you to select one from the list. Be sure to use the same key that you signed your git tag with. b. Log in to the server via SSH and check for releases that can be promoted, along with the list of artifacts. It will use the `dist-promotable` command on the server to find these. You will be asked, for each promotable release, whether you want to proceed. If there is more than one release to promote (there shouldn't be), be sure to only promote the release you are responsible for. c. Log in to the server via SSH and run the promote script for the given release. The command on the server will be similar to: `dist-promote vx.y.z`. After this step, the release artifacts will be available for download and a `SHASUMS256.txt` file will be present. The release will still be unsigned, however. d. Use `scp` to download `SHASUMS256.txt` to a temporary directory on your computer. e. Sign the `SHASUMS256.txt` file using a command similar to: `gpg --default-key YOURKEY --digest-algo SHA256 --clearsign /path/to/SHASUMS256.txt`. You will be prompted by GPG for your password. The signed file will be named SHASUMS256.txt.asc. f. Output an ASCII armored version of your public GPG key using a command similar to: `gpg --default-key YOURKEY --digest-algo SHA256 --detach-sign /path/to/SHASUMS256.txt`. You will be prompted by GPG for your password. The signed file will be named SHASUMS256.txt.sig. g. Upload the `SHASUMS256.txt` files back to the server into the release directory. </details> It is possible to only sign a release by running `./tools/release.sh -s vX.Y.Z`. ### 16. Check the release Your release should be available at `https://nodejs.org/dist/vx.y.z/` and <https://nodejs.org/dist/latest/>. Check that the appropriate files are in place. You may want to check that the binaries are working as appropriate and have the right internal version strings. Check that the API docs are available at <https://nodejs.org/api/>. Check that the release catalog files are correct at <https://nodejs.org/dist/index.tab> and <https://nodejs.org/dist/index.json>. ### 17. Create a blog post There is an automatic build that is kicked off when you promote new builds, so within a few minutes nodejs.org will be listing your new version as the latest release. However, the blog post is not yet fully automatic. Create a new blog post by running the [nodejs.org release-post.js script][]: ```bash node ./apps/site/scripts/release-post/index.mjs x.y.z ``` This script will use the promoted builds and changelog to generate the post. Run `npm run serve` to preview the post locally before pushing to the [nodejs.org repository][]. * You can add a short blurb just under the main heading if you want to say something important, otherwise the text should be publication ready. * The links to the download files won't be complete unless you waited for the ARMv6 builds. Any downloads that are missing will have `Coming soon` next to them. It's your responsibility to manually update these later when you have the outstanding builds. * The `SHASUMS256.txt.asc` content is at the bottom of the post. When you update the list of tarballs you'll need to copy/paste the new contents of this file to reflect those changes. * Always use pull-requests on the [nodejs.org repository][]. Be respectful of the website team, but you do not have to wait for PR sign-off. Please use the following commit message format: ```console Blog: vX.Y.Z release post Refs: <full URL to your release proposal PR> ``` * In order to trigger the CI Checks of the [nodejs.org repository][]; Please attach the `github_actions:pull-request` label to the PR. * Changes to the base branch, `main`, on the [nodejs.org repository][] will trigger a new build of nodejs.org, so your changes should appear a few minutes after pushing. You can follow the [Deployments](https://github.com/nodejs/nodejs.org/deployments) page to see when the build finishes and gets published. ### 18. Create the release on GitHub * Go to the [New release page](https://github.com/nodejs/node/releases/new). * Select the tag version you pushed earlier. * For release title, copy the title from the changelog. * For the description, copy the rest of the changelog entry. * If you are not releasing the latest "Current", uncheck "Set as the latest release". * Click on the "Publish release" button. ### 19. Announce The nodejs.org website will automatically rebuild and include the new version. To announce the build on social media, please ping the @nodejs-social-team on offical slack channel. Node.js is also available on Bluesky and a release announcement can be reposted using [nodejs/bluesky](https://github.com/nodejs/bluesky) repository. The post content can be as simple as: > v5.8.0 of @nodejs is out: <https://nodejs.org/en/blog/release/v5.8.0/> > … > something here about notable changes <details> <summary>Security release</summary> Let the security release steward know the releases are available. </details> ### 20. Celebrate _In whatever form you do this..._ ## LTS Releases ### Marking a release line as LTS The process of marking a release line as LTS has been automated using [`@node-core/utils`](https://github.com/nodejs/node-core-utils). Start by checking out the staging branch for the release line that is going to be marked as LTS, e.g: ```bash git checkout v1.x-staging ``` Next, make sure you have `@node-core/utils` installed: ```bash npm i -g @node-core/utils ``` Run the prepare LTS release command: ```bash git node release --prepare --startLTS ``` <details> <summary>Manual steps for reference.</summary> To mark a release line as LTS, the following changes must be made to `src/node_version.h`: * The `NODE_MINOR_VERSION` macro must be incremented by one * The `NODE_PATCH_VERSION` macro must be set to `0` * The `NODE_VERSION_IS_LTS` macro must be set to `1` * The `NODE_VERSION_LTS_CODENAME` macro must be set to the code name selected for the LTS release. For example: ```diff -#define NODE_MINOR_VERSION 12 -#define NODE_PATCH_VERSION 1 +#define NODE_MINOR_VERSION 13 +#define NODE_PATCH_VERSION 0 -#define NODE_VERSION_IS_LTS 0 -#define NODE_VERSION_LTS_CODENAME "" +#define NODE_VERSION_IS_LTS 1 +#define NODE_VERSION_LTS_CODENAME "Erbium" -#define NODE_VERSION_IS_RELEASE 0 +#define NODE_VERSION_IS_RELEASE 1 ``` The changes must be made as part of a new semver-minor release. Updating changelogs to properly reflect the changes between Current and Long Term Support is also necessary, along with adding a reference to the current LTS codename in its release line changelog file. The `test/parallel/test-process-release.js` file might also need to be updated. In case you can not run the automated `@node-core/utils` command and you are currently running these steps manually it's a good idea to refer to previous LTS proposal PRs and make sure all required changes are covered. </details> ### Update release labels The `lts-watch-vN.x` issue label must be created, with the same color as other existing labels for that release line, such as `vN.x`. If the release is transitioning from Active LTS to Maintenance, the `backport-requested-vN.x` label must be deleted. ### Add new codename to nodejs-latest-linker In order to make sure a download URL (e.g: <https://nodejs.org/download/release/latest-codename/>) will be available for the new LTS release line you need to submit a PR to <https://github.com/nodejs/nodejs-latest-linker> and add a new entry for the new LTS codename in its `ltsNames` map located in the `./common.js` file. Make sure to reach out to the Build WG in order to validate that the new URL is available as part of the LTS release promotion. ### Update Release repo info Add the new LTS codename to the release schedule table located in the `./README.md` file located at the <https://github.com/nodejs/Release> repository along with the addition of the new codename to the `./schedule.json` file in that same repo. ## Major releases The process for cutting a new Node.js major release has a number of differences from cutting a minor or patch release. ### Schedule New Node.js Major releases happen twice per year: * Even-numbered releases are cut in April. * Odd-numbered releases are cut in October. Major releases should be targeted for the third Tuesday of the release month. A major release must not slip beyond the release month. In other words, major releases must not slip into May or November. The @nodejs/releasers make a call for releasers 3 months in advance. Currently, this call is automated in the `#nodejs-release-private` Slack channel. The release date for the next major release should be announced immediately following the current release (e.g. the release date for 13.0.0 should be announced immediately following the release of 12.0.0). ### Release branch Approximately two months before a major release, new `vN.x` and `vN.x-staging` branches (where `N` indicates the major release) should be created as forks of the `main` branch. Up until the cut-off date announced by the releaser, these must be kept in sync with `main`. The `vN.x` and `vN.x-staging` branches must be kept in sync with one another up until the date of the release. If a `SEMVER-MAJOR` pull request lands on the default branch within one month prior to the major release date, it must not be included on the new major staging branch, unless there is consensus from the Node.js releasers team to do so. This measure aims to ensure better stability for the release candidate (RC) phase, which begins approximately two weeks prior to the official release. By restricting `SEMVER-MAJOR` commits in this period, we provide more time for thorough testing and reduce the potential for major breakages, especially in LTS lines. ### Create release labels The following issue labels must be created: * `vN.x` * `backport-blocked-vN.x` * `backport-open-vN.x` * `backport-requested-vN.x` * `backported-to-vN.x` * `dont-land-on-vN.x` The label description can be copied from existing labels of previous releases. The label color must be the same for all new labels, but different from the labels of previous releases. ### Release proposal A draft release proposal should be created 6 weeks before the release. A separate `vN.x-proposal` branch should be created that tracks the `vN.x` branch. This branch will contain the draft release commit (with the draft changelog). Notify the `@nodejs/npm` team in the release proposal PR to inform them of the upcoming release. `npm` maintains a list of [supported versions](https://github.com/npm/cli/blob/latest/lib/utils/unsupported.js#L3) that will need updating to include the new major release. To keep the branch in sync until the release date, it can be as simple as doing the following: > Make sure to check that there are no PRs with the label `dont-land-on-vX.x`. ```bash git checkout vN.x git reset --hard upstream/main git checkout vN.x-staging git reset --hard upstream/main git push upstream vN.x git push upstream vN.x-staging ``` ### Update `NODE_MODULE_VERSION` This macro in `src/node_version.h` is used to signal an ABI version for native addons. It currently has two common uses in the community: * Determining what API to work against for compiling native addons, e.g. [NAN](https://github.com/nodejs/nan) uses it to form a compatibility-layer for much of what it wraps. * Determining the ABI for downloading pre-built binaries of native addons, e.g. [node-pre-gyp](https://github.com/mapbox/node-pre-gyp) uses this value as exposed via `process.versions.modules` to help determine the appropriate binary to download at install-time. The general rule is to bump this version when there are _breaking ABI_ changes and also if there are non-trivial API changes. The rules are not yet strictly defined, so if in doubt, please confer with someone that will have a more informed perspective, such as a member of the NAN team. A registry of currently used `NODE_MODULE_VERSION` values is maintained at <https://github.com/nodejs/node/blob/HEAD/doc/abi_version_registry.json>. When bumping `NODE_MODULE_VERSION`, you should choose a new value not listed in the registry. Also include a change to the registry in your commit to reflect the newly used value. Ensure that the release commit removes the `-pre` suffix for the major version being prepared. It is current TSC policy to bump major version when ABI changes. If you see a need to bump `NODE_MODULE_VERSION` outside of a major release then you should consult the TSC. Commits may need to be reverted or a major version bump may need to happen. ### Test releases and release candidates Test builds should be generated from the `vN.x-proposal` branch starting at about 6 weeks before the release. Release Candidates should be generated from the `vN.x-proposal` branch starting at about 4 weeks before the release, with a target of one release candidate per week. Always run test releases and release candidates through the Canary in the Goldmine tool for additional testing. ### Changelogs Generating major release changelogs is a bit more involved than minor and patch changelogs. #### Create the changelog file In the `doc/changelogs` directory, create a new `CHANGELOG_V{N}.md` file where `{N}` is the major version of the release. Follow the structure of the existing `CHANGELOG_V.md` files. The navigation headers in all of the `CHANGELOG_V.md` files must be updated to account for the new `CHANGELOG_V{N}.md` file. Once the file is created, the root `CHANGELOG.md` file must be updated to reference the newly-created major release `CHANGELOG_V{N}.md`. #### Generate the changelog To generate a proper major release changelog, use the `branch-diff` tool to compare the `vN.x` branch against the `vN-1.x` branch (e.g. for Node.js 12.0, we compare the `v12.x` branch against the up to date `v11.x` branch). Make sure that the local copy of the downlevel branch is up to date. The commits in the generated changelog must then be organized: * Remove all release commits from the list * Remove all reverted commits and their reverts * Separate all SEMVER-MAJOR, SEMVER-MINOR, and SEMVER-PATCH commits into lists ```console $ branch-diff upstream/vN-1.x upstream/vN.x --require-label=semver-major --group --filter-release # get all majors $ branch-diff upstream/vN-1.x upstream/vN.x --require-label=semver-minor --group --filter-release # get all minors $ branch-diff upstream/vN-1.x upstream/vN.x --exclude-label=semver-major,semver-minor --group --filter-release # get all patches ``` #### Generate the notable changes For a major release, all SEMVER-MAJOR commits that are not strictly internal, test, or doc-related are to be listed as notable changes. Some SEMVER-MINOR commits may be listed as notable changes on a case-by-case basis. Use your judgment there. ### Update the expected assets The promotion script does a basic check that the expected files are present. Open a pull request in the Build repository to add the list of expected files for the new release line as a new file, `v{N}.x` (where `{N}` is the major version of the release), in the [expected assets][] folder. The change will need to be deployed onto the web server by a member of the [build-infra team][] before the release is promoted. ### Snap The Node.js [Snap][] package has a "default" for installs where the user hasn't specified a release line ("track" in Snap terminology). This should be updated to point to the most recently activated LTS. A member of the Node.js Build Infrastructure team is able to perform the switch of the default. An issue should be opened on the [Node.js Snap management repository][] requesting this take place once a new LTS line has been released. ## FAQ Due to how `tools/release.sh` work, it isn't uncommon to face some errors during the promotion process as it depends on network communication and machine availability. This section aims to guide the releaser through potential failures. ### Error on dist-indexer while promoting ```bash node:events:491 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) Emitted 'error' event on DestroyableTransform instance at: at ClientRequest.<anonymous> (/usr/lib/node_modules/nodejs-dist-indexer/node_modules/hyperquest/index.js:14:19) at ClientRequest.emit (node:events:513:28) at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -104, code: 'ECONNRESET', syscall: 'read' } ``` Typical resolution: sign the release again. ```bash ./tools/release.sh -s vX.Y.Z ``` [Build issue tracker]: https://github.com/nodejs/build/issues/new [CI lockdown procedure]: https://github.com/nodejs/build/blob/HEAD/doc/jenkins-guide.md#restricting-access-for-security-releases [Node.js Snap management repository]: https://github.com/nodejs/snap [Snap]: https://snapcraft.io/node [`create-release-proposal`]: https://github.com/nodejs/node/actions/workflows/create-release-proposal.yml [build-infra team]: https://github.com/orgs/nodejs/teams/build-infra [expected assets]: https://github.com/nodejs/build/tree/HEAD/ansible/www-standalone/tools/promote/expected_assets [nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/apps/site/scripts/release-post/index.mjs [nodejs.org repository]: https://github.com/nodejs/nodejs.org	50.22 KB	2025-02-28 19:16
📄 security-model-strategy.md # Security Model Strategy A clear security model, with features like permissions and policy enforcement, is a [top technical priority](https://github.com/nodejs/node/blob/HEAD/doc/contributing/technical-priorities.md#permissionspoliciessecurity-model) of Node.js. ## High-level approach * Document the security model * Document threat models and current state of the art * Support experimentation on features like permissions and policies * Add a security component in Node.js certification covering the Node.js security model ### Document the security model The current security model for Node.js is not yet well documented. At a high level it is: * Node.js does not provide a sandbox, both the JavaScript and native code which is run is trusted to not be malicious. * The project works to help code running on top of Node.js to avoid making mistakes, but not doing so is not considered a vulnerability in Node.js. Just because you can build something vulnerable with the APIs does not mean there is a vulnerability in Node.js itself. The project has a goal to better document the security model and this section will be expanded when that happens. Once the security model is documented the project will work to add a security component in Node.js certification covering the Node.js security model. ### Document threat models and current state of the art Node.js is used in several different use cases and the threats may be different in each use case. The project should document the threat models and use that to help define the security model in the context of each of these use cases. This section will be expanded as the use case/threat models are defined. The initial list includes: * Server * Desktop application * Cli * Single executable application * CI/CD pipeline components ### Support experimentation on features like permissions The project is not currently planning to provide supported sandbox functionality, but wants to support experimentation on related features like permission enforcement. Features in this category should: * be opt-in, and additional overhead when not enabled must be low * limit change in core to just what is needed to enable experimentation	2.16 KB	2025-02-28 19:16
📄 security-release-process.md # Security release process The security release process covers the steps required to plan/implement a security release. This document is copied into the description of the Next Security Release and used to track progress on the release. It contains _TEXT LIKE THIS_ which will be replaced during the release process with the information described. ## Security release stewards For each security release, a security steward will take ownership for coordinating the steps outlined in this process. Security stewards are nominated through an issue in the TSC repository and approved through the regular TSC consensus process. Once approved, they are given access to all of the resources needed to carry out the steps listed in the process as outlined in [security steward on/off boarding](security-steward-on-off-boarding.md). The current security stewards are documented in the main Node.js [README.md](https://github.com/nodejs/node#security-release-stewards). \| Company \| Person \| Release Date \| \| ------------ \| --------------- \| ------------ \| \| NearForm \| Matteo \| 2021-Oct-12 \| \| Datadog \| Bryan \| 2022-Jan-10 \| \| RH and IBM \| Joe \| 2022-Mar-18 \| \| NearForm \| Matteo / Rafael \| 2022-Jul-07 \| \| Datadog \| Vladimir \| 2022-Sep-23 \| \| NodeSource \| Juan \| 2022-Nov-04 \| \| RH and IBM \| Michael \| 2023-Feb-16 \| \| NearForm \| Rafael \| 2023-Jun-20 \| \| NearForm \| Rafael \| 2023-Aug-09 \| \| NearForm \| Rafael \| 2023-Oct-13 \| \| NodeSource \| Rafael \| 2024-Feb-14 \| \| NodeSource \| Rafael \| 2024-Apr-03 \| \| NodeSource \| Rafael \| 2024-Apr-10 \| \| NodeSource \| Rafael \| 2024-Jul-08 \| \| Datadog \| Bryan \| \| \| IBM \| Joe \| \| \| Platformatic \| Matteo \| \| \| NodeSource \| Juan \| \| \| Red Hat \| Michael \| \| ## Planning * [ ] 1\. Generating Next Security Release PR * Run `git node security --start` inside [security-release][] repository. * This command generates a new `vulnerabilities.json` file with HackerOne reports chosen to be released in the `security-release/next-security-release` folder. * It also creates the pull request used to manage the security release. * [ ] 2\. Review of Reports: * Reports can be added or removed using the following commands: * Use the "summary" feature in HackerOne. Example [2038134](https://hackerone.com/reports/2038134) * `git node security --add-report=report_id` * `git node security --remove-report=report_id` * [ ] 3\. Assigning Severity and Writing Team Summary: * [ ] Assign a severity and write a team summary on HackerOne for the reports chosen in the `vulnerabilities.json`. * Run `git node security --sync` to update severity and summary in `vulnerabilities.json`. * [ ] 4\. Requesting CVEs: * Request CVEs for the reports with `git node security --request-cve`. * Make sure to have a green CI before requesting a CVE. * [ ] 5\. Choosing or Updating Release Date: * Get agreement on the planned date for the release. * [ ] Use `git node security --update-date=YYYY/MM/DD` to choose or update the release date. * This allows flexibility in postponing the release if needed. * [ ] 6\. Get release volunteers: * Get volunteers for the upcoming security release on the affected release lines. * [ ] 7\. Preparing Pre and Post Release Blog Posts: * [ ] Create a pre-release blog post using `git node security --pre-release`. * [ ] Create a post-release blog post using `git node security --post-release`. ## Announcement (one week in advance of the planned release) * [ ] 1\. Publish Pre-Release Blog Post: * Publish the pre-release blog post on the `nodejs/nodejs.org` repository. * [ ] 2\. Send Pre-Release Announcement: * Notify the community about the upcoming security release: * [ ] `git node security --notify-pre-release` Except for those noted in the list below, this will create automatically the issues and emails needed for the notifications. * [docker-node](https://github.com/nodejs/docker-node/issues) * [build-wg](https://github.com/nodejs/build/issues) * [ ] (Not yet automatic - do this manually) [Google Groups](https://groups.google.com/g/nodejs-sec) * Email: notify <oss-security@lists.openwall.com> * [ ] (Not yet automatic - do this manually) Post in the nodejs-social channel in the OpenJS slack asking for amplification of the blog post. ```text Security release pre-alert: We will release new versions of <add versions> release lines on or shortly after Day Month Date, Year in order to address: * # high severity issues * # moderate severity issues https://nodejs.org/en/blog/vulnerability/month-year-security-releases/ ``` We specifically ask that collaborators other than the releasers and security steward working on the security release do not tweet or publicize the release until the tweet from Node.js goes out. We have often seen tweets sent out before the release is complete, which may confuse those waiting for the release and take away from the work the releasers have put into shipping the release. If the security release will only contain an OpenSSL update, consider adding the following to the pre-release announcement: ```text Since this security release will only include updates for OpenSSL, if you're using a Node.js version which is part of a distribution that uses a system installed OpenSSL, this Node.js security update may not concern you, instead, you may need to update your system OpenSSL libraries. Please check the security announcements for more information. ``` ## Release day * [ ] 1\. Lock down the CI: * Lock down the CI to prevent public access to the CI machines, ping a member of `@nodejs/jenkins-admins`. * [ ] 2\. Release: * Verify the CI is green on all release proposals (test-V8, CITGM, etc). * Follow the [release process](https://github.com/nodejs/node/blob/main/doc/contributing/releases.md). * [ ] 3\. Unlock the CI: * Unlock the CI to allow public access to the CI machines, ping a member of `@nodejs/jenkins-admins`. * [ ] 4\. Publish Post-Release Blog Post: * Publish the post-release blog post on the `nodejs/nodejs.org` repository. * [ ] 5\. Notify the community: * Notify the community that the security release has gone out: * [ ] Slack: `#nodejs-social` * [ ] [docker-node](https://github.com/nodejs/docker-node/issues) * [ ] [build-wg](https://github.com/nodejs/build/issues) * [ ] Email: notify [Google Groups](https://groups.google.com/g/nodejs-sec) * Forward to <oss-security@lists.openwall.com> ## Post-Release * [ ] 1\. Merge the Next Security Release PR: * This involves moving the `vulnerabilities.json` file from `security-release/next-security-release` to the `security-release/YYYY-MM-DD` folder and merging the PR. * [ ] 2\. Cleanup: * [ ] `git node security --cleanup`. This command will: * Close PRs and backports. * Close HackerOne reports: * Close Resolved * Request Disclosure * Request publication of H1 CVE requests * In case the reporter doesn't accept the disclosure follow this process: Remove the original report reference within the reference text box and insert the public URL you would like to be attached to this CVE. Then uncheck the Public Disclosure on HackerOne box at the bottom of the page. ![screenshot of HackerOne CVE form](https://github.com/nodejs/node/assets/26234614/e22e4f33-7948-4dd2-952e-2f9166f5568d) * [ ] PR machine-readable JSON descriptions of the vulnerabilities to the [core](https://github.com/nodejs/security-wg/tree/HEAD/vuln/core) vulnerability DB. * [ ] Add yourself as a steward in the [Security Release Stewards](https://github.com/nodejs/node/blob/HEAD/doc/contributing/security-release-process.md#security-release-stewards) ## Adding a security revert option Breaking changes are allowed in existing LTS lines in order to fix important security vulnerabilities. When breaking changes are made it is important to provide a command line option that restores the original behaviour. The existing Node.js codebase supports the command line option `--security-revert` and has the boilerplate to make additions for a specific CVE easy. To add an option to revert for a CVE, for example `CVE-2024-1234` simply add this line to [`node_revert.h`](https://github.com/nodejs/node/blob/main/src/node_revert.h) ```c XX(CVE_2024_1234, "CVE-2024-1234", "Description of cve") ``` This will allow an easy check of whether a reversion has been requested or not. In JavaScript code you can check: ```js if (process.REVERT_CVE_2024_1234); ``` In C/C++ code you can check: ```c IsReverted(SECURITY_REVERT_CVE_2024_1234) ``` From the command line a user can request the revert by using the `--security-revert` option as follows: ```console node --security-revert=CVE-2024-1234 ``` If there are multiple security reverts then multiple instances of --security-revert can be used. For example: ```console node --security-revert=CVE-2024-1234 --security-revert=CVE-2024-XXXX ``` ## When things go wrong ### Incomplete fixes When a CVE is reported as fixed in a security release and it turns out that the fix was incomplete, a new CVE should be used to cover subsequent fix. This is best practice and avoids confusion that might occur if people believe they have patched the original CVE by updating their Node.js version and then we later change the `fixed in` value for the CVE. ### Updating CVEs The steps to correct CVE information are: * Go to the “CVE IDs” section in your program sections (<https://hackerone.com/nodejs/cve_requests>) * Click the “Request a CVE ID” button * Enter the CVE ID that needs to be updated * Include all the details that need updating within the form * Submit the request [security-release]: https://github.com/nodejs-private/security-release	10.01 KB	2025-02-28 19:16
📄 security-steward-on-off-boarding.md # Security Steward Onboarding/OffBoarding ## Onboarding * Confirm the new steward agrees to keep all private information confidential to the project and not to use/disclose to their employer. * Add them to the security-stewards team in the GitHub nodejs-private organization. * Add them to the [public website team](https://github.com/orgs/nodejs/teams/website). * Ensure they have 2FA enabled in H1. * Add them to the standard team in H1 using this [page](https://hackerone.com/nodejs/team_members). * Add them as managers of the [nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list. ## Offboarding * Remove them from security-stewards team in the GitHub nodejs-private organization. * Remove them from public website team * Unless they have access for another reason, remove them from the standard team in H1 using this [page](https://hackerone.com/nodejs/team_members). * Downgrade their account to regular member in the [nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list.	1.02 KB	2025-02-28 19:16
📄 sharing-project-news.md # Sharing project news The project aims to make it easy to share project news with those who publish newsletters that cover Node.js. The project's approach is as follows: * The project will create one "What's new in YYYY" discussion item in the `nodejs/node` repo for news related to Node.js core. * Teams/groups can create a "what's new in YYYY" issue or discussion item in one or more of their repositories. As an example see [What's new in the Node-API and node-addon-api world? - 2023 version](https://github.com/nodejs/abi-stable-node/issues/446). * Collaborators periodically add news as additional comments on these issues throughout the year. * At the end of each year the issue is closed and if appropriate a new one is created. * A list of these documents is maintained in the section below as a quick way to find them. * The next-10 team reaches out to teams/groups on an ad hoc basis to ensure teams know about the option for sharing news. * The next-10 team reaches out to those who publish newsletters ad hoc to let them know about this approach and how they can find the updates. We trust/expect collaborators to post project related news versus news that promotes a specific company or commercial interest. ## Teams doing updates * [node-api/node-addon-api](https://github.com/nodejs/abi-stable-node/issues/459). * [uvwasi](https://github.com/nodejs/uvwasi/issues/201). * [Website team](https://github.com/nodejs/nodejs.org/issues/5602). * [diagnostics team](https://github.com/nodejs/diagnostics/issues/619). * [ambassadors](https://github.com/nodejs/nodejs-ambassadors/issues/2).	1.58 KB	2025-02-28 19:16
📄 static-analysis.md # Static Analysis The project uses Coverity to scan Node.js source code and to report potential issues in the C/C++ code base. Those who have been added to the [Node.js coverity project][] can receive emails when there are new issues reported as well as view all current issues through <https://scan9.scan.coverity.com/reports.htm>. Any collaborator can ask to be added to the Node.js coverity project by opening an issue in the [build][] repository titled `Please add me to coverity`. A member of the build WG with admin access will verify that the requestor is an existing collaborator as listed in the [collaborators section][] on the nodejs/node project repo. Once validated the requestor will be added to the coverity project. [Node.js coverity project]: https://scan.coverity.com/projects/node-js [build]: https://github.com/nodejs/build [collaborators section]: https://github.com/nodejs/node#collaborators	918 B	2025-02-28 19:16
📄 strategic-initiatives.md # Strategic initiatives The Node.js project has several strategic initiatives underway. A review of the current initiatives is a standing item on the Technical Steering Committee agenda to ensure they are active and have the support they need. ## Current initiatives \| Initiative \| Champion \| Links \| \| ---------------------- \| -------------------------------- \| ------------------------------------------------- \| \| Core Promise APIs \| [Antoine du Hamel][aduh95] \| <https://github.com/nodejs/TSC/issues/1094> \| \| QUIC / HTTP3 \| [James M Snell][jasnell] \| <https://github.com/nodejs/quic> \| \| Shadow Realm \| [Chengzhong Wu][legendecas] \| <https://github.com/nodejs/node/issues/42528> \| \| Startup Snapshot \| [Joyee Cheung][joyeecheung] \| <https://github.com/nodejs/node/issues/35711> \| \| V8 Currency \| [Michaël Zasso][targos] \| \| \| Next-10 \| [Michael Dawson][mhdawson] \| <https://github.com/nodejs/next-10> \| \| Single executable apps \| \| <https://github.com/nodejs/node/issues/43432> \| \| Performance \| \| <https://github.com/nodejs/performance> \| \| Primordials \| [Benjamin Gruenbaum][benjamingr] \| <https://github.com/nodejs/primordials-use-cases> \| <details> <summary>List of completed initiatives</summary> ## Completed initiatives \| Initiative \| Champion \| Links \| \| ------------------ \| -------------------------- \| -------------------------------------------------------------------- \| \| Build resources \| Michael Dawson \| <https://github.com/nodejs/build/issues/1154#issuecomment-448418977> \| \| CVE Management \| Michael Dawson \| <https://github.com/nodejs/security-wg/issues/33> \| \| Governance \| Myles Borins \| \| \| Moderation Team \| Rich Trott \| <https://github.com/nodejs/TSC/issues/329> \| \| Modules \| Myles Borins \| <https://github.com/nodejs/modules> \| \| N-API \| Michael Dawson \| <https://github.com/nodejs/abi-stable-node> \| \| npm Integration \| Myles Borins \| <https://github.com/nodejs/node/pull/21594> \| \| OpenSSL Evolution \| Rod Vagg \| <https://github.com/nodejs/TSC/issues/677> \| \| Open Web Standards \| Myles Borins, Joyee Cheung \| <https://github.com/nodejs/open-standards> \| \| VM module fix \| Franziska Hinkelmann \| <https://github.com/nodejs/node/issues/6283> \| \| Workers \| Anna Henningsen \| <https://github.com/nodejs/worker> \| </details> [aduh95]: https://github.com/aduh95 [benjamingr]: https://github.com/benjamingr [jasnell]: https://github.com/jasnell [joyeecheung]: https://github.com/joyeecheung [legendecas]: https://github.com/legendecas [mhdawson]: https://github.com/mhdawson [targos]: https://github.com/targos	3.43 KB	2025-02-28 19:16
📄 streaming-to-youtube.md # Streaming Meetings to Youtube We publicly live stream our meetings to YouTube using [Zoom](https://zoom.us/). ## Getting Access You need the Foundation login credentials for Zoom in order to host the meeting. The userid and password is shared through 1password. Your YouTube Account must be a manager of the [Node.js YouTube account](https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ). To request access open an issue in the Node.js [admin](https://github.com/nodejs/admin) repository with the title being `Zoom and Youtube access for X` where X is the GitHub id and the YouTube ID of the person for which access is being requested. Include a short reason why access is needed(for example streaming a team meeting etc.). Unless there are objections the request is considered approved after 48 hours. ## Managing access ### Youtube To add managers or verify an account is a manager: 1. Go to <https://youtube.com> 2. Click on the Node.js icon on the right top. 3. Select settings, select "Add or remove managers", select "Manage permissions" 4. On that page you can use the +people at the top right of the popup to add people. It also lists all current managers. ### Zoom To share the Zoom password log into 1password, select the settings gear for the`zoom-creds` vault and then use `Share Vault` to share the vault with the new user. Use the gear to set the permissions to include only `View Items` and `View and Copy passwords`. When adding access for a user also ask them to create a PR adding themselves to the `zoom-nodejs` group in the [iojs.org/aliases.json](https://github.com/nodejs/email/blob/main/iojs.org/aliases.json) file [nodejs/email](https://github.com/nodejs/email/) ## Live streaming a meeting ### Start and Stop the stream 1. Login to <https://zoom.us> using the Foundation credentials. 2. Go to <https://zoom.us/webinar/list>, find the meeting. 3. Press "Start", it should open the meeting in the Zoom application. 4. Go to "Participants" panel, check Attendees, promote them to panelists. 5. Go to "... More" in toolbar, choose "Live on YouTube", it will open in browser. 6. Choose to login to <https://youtube.com> with Node.js account, accept Zoom usage agreement (on first use) 7. On the Streaming page, edit the webinar title to include the meeting date, then press the red "Go Live!" button. Troubleshooting note: at least one person has found that "Go Live!" errored with a message "Please grant necessary privilege for live streaming". Copying the link from the default browser to a different browser may work around this issue. Every participant can choose whether to participate with or without video. YouTube records the live stream. Recordings are made available on the [Node.js channel](https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ/videos). The stream title is set automatically from the information in Zoom. We usually set it to `YYYY-MM-DD - Meeting Name` for example `2022-11-02 - Technical Steering Community Meeting`. The description should be a link to the meeting issue. You can edit title and description on YouTube at a later time if needed. ![YouTube Basic Info example text](./doc_img/youtube-stream-title-description.png) ### Share the meeting once you've gone live The meeting link should be `http://www.youtube.com/c/nodejs-foundation/live`. Send it in a tweet such as: ```text .@nodejs Technical Steering Committee meeting live now: http://www.youtube.com/c/nodejs-foundation/live ``` Adjust the `Technical Steering Committee` part as necessary and remove the `.@nodejs` if tweeting from the official twitter account. ![YouTube Share input box](./doc_img/youtube-stream-share.png) ## Check stream status This should say online when you are streaming, and usually be green. However, it may turn yellow and issue a warning in a "stream health" section below. Since we usually stream with static images for the video, there will often be warnings that the video bitrate is low. This is a not a problem and should almost always be ignored. ![YouTube Stream Status showing Offline](./doc_img/youtube-stream-status.png) ## Check how many people are watching ![YouTube Analytics graph](./doc_img/youtube-stream-analytics.png) ## Moderate the chat and solicit questions Moderation follows the [Moderation Policy](https://github.com/nodejs/admin/blob/main/Moderation-Policy.md). Messages can be moderated right-clicking and selecting the necessary action, such as `remove`. If you participate in the chat while logged in as Node.js, it's good practice to append your initials to your messages.	4.51 KB	2025-02-28 19:16
📄 suggesting-social-media-posts.md # Suggesting Social Media Posts Node.js social media is managed by OpenJS Foundation staff. The processes are documented in [Node.js Social Amplification Request Guidelines](https://docs.google.com/document/d/1yrYZJ2twrbpUuScbo3rmN_v-Jfv6d2tO74nCT6PcpxI).	257 B	2025-02-28 19:16
📄 technical-priorities.md # Technical Priorities This list represents the current view of key technical priorities recognized by the project as important to ensure the ongoing success of Node.js. It is based on an understanding of the Node.js [constituencies](https://github.com/nodejs/next-10/blob/main/CONSTITUENCIES.md) and their [needs](https://github.com/nodejs/next-10/blob/main/CONSTITUENCY-NEEDS.md). The initial version was created based on the work of the [Next-10 team](https://github.com/nodejs/next-10) and the [mini-summit](https://github.com/nodejs/next-10/issues/76) on August 5th 2021. They will be updated regularly and will be reviewed by the next-10 team and the TSC on a 6-month basis. Version from the [mini-summit](https://github.com/nodejs/next-10/issues/1) on October 1st 2022. ## Modern HTTP _Present in: 2021_ Base HTTP support is a key component of modern cloud-native applications, and built-in support was part of what made Node.js a success in the first 10 years. The current implementation is hard to support and a common source of vulnerabilities. We must work towards an implementation that is easier to support and makes it easier to integrate the new HTTP versions (HTTP3, QUIC) and to support efficient implementations of different versions concurrently. ## Suitable types for end-users _Present in: 2021_ Using typings with JavaScript can allow a richer experience when using Visual Studio Code (or any other IDEs) environments, more complete documentation of APIs and the ability to identify and resolve errors earlier in the development process. These benefits are important to a large number of Node.js developers (maybe 50%). Further typing support may be important to enterprises that are considering expanding their preferred platforms to include Node.js. It is, therefore, important that the Node.js project work to ensure there are good typings available for the public Node.js APIs. ## Documentation _Present in: 2021_ The current documentation is great for experienced developers or people who are aware of what they are looking for. On the other hand, for beginners this documentation can be quite hard to read and finding the desired information is difficult. We must have documentation that is suitable for beginners to continue the rapid growth in use. This documentation should include more concrete examples and a learning path for newcomers. ## WebAssembly _Present in: 2021_ The use of WebAssembly has been growing over the last few years. To ensure Node.js continues to be part of solutions where a subset of the solution needs the performance that WebAssembly can deliver, Node.js must provide good support for running WebAssembly components along with the JavaScript that makes up the rest of the solution. This includes implementations of “host” APIs like WASI. ## ES Modules (ESM) _Present in: 2021_ The CommonJS module system was one of the key components that led to the success of Node.js in its first 10 years. ESM is the standard that has been adopted as the equivalent in the broader JavaScript ecosystem and Node.js must continue to develop and improve its ESM implementation to stay relevant and ensure continued growth for the next 10 years. ## Support for features from the latest ECMAScript spec JavaScript developers are a fast moving group and need/want support for new ES JavaScript features in a timely manner. Node.js must continue to provide support for up to date ES versions to remain the runtime of choice and to ensure its continued growth for the next 10 years. ## Observability _Present in: 2021_ The ability to investigate and resolve problems that occur in applications running in production is crucial for organizations. Tools that allow people to observe the current and past operation of the application are needed to support that need. It is therefore important that the Node.js project work towards well understood and defined processes for observing the behavior of Node.js applications as well as ensuring there are well supported tools to implement those processes (logging, metrics and tracing). This includes support within the Node.js runtime itself (for example generating heap dumps, performance metrics, etc.) as well as support for applications on top of the runtime. In addition, it is also important to clearly document the use cases, problem determination methods, and best practices for those tools. ## Better multithreaded support _Present in: 2021_ Today's servers support multiple threads of concurrent execution. Node.js deployments must be able to make full and efficient use of the available resources. The right answer is often to use technologies like containers to run multiple single threaded Node.js instances on the same server. However, there are important use cases where a single Node.js instance needs to make use of multiple threads to achieve a performant and efficient implementation. In addition, even when a Node.js instance only needs to consume a single thread to complete its work there can be issues. If that work is long running, blocking the event loop will interfere with other supporting work like metrics gathering and health checks. Node.js must provide good support for using multiple threads to ensure the continued growth and success of Node.js. ## Single Executable Applications Node.js often loses out to other runtimes/languages in cases where being able to package a single, executable application simplifies distribution and management of what needs to be delivered. While there are components/approaches for doing this, they need to be better documented and evangelized so that this is not seen as a barrier for using Node.js in these situations. This is important to support the expansion of where/when Node.js is used in building solutions. ## Serverless Serverless is a cloud computing model where the cloud provider manages the underlying infrastructure and automatically allocates resources as needed. Developers only need to focus on writing code for specific functions, which are executed as individual units of work in response to events. Node.js is one of the main technology used by developers in this field therefore it is crucial for us to provide a great solution. ## Small footprint Small software footprints refer to software that has a minimal impact on system resources such as memory and processing power. This can be achieved through various methods such as optimizing code, reducing the number of dependencies, or using lightweight frameworks. Smaller footprints can lead to faster startup times, reduced memory usage, and improved overall system performance. This is fundamental for Node.js to be a lightweight proposition inside the ecosystem as it is used across a wild variety of projects, from web application to IoT and serverless. ## Developers-first DX Developer experience (DX) refers to the overall experience a developer has when working with a software development platform, framework, or tool. It encompasses all aspects of the developer's interactions with the system, from installation and configuration to writing code and debugging. A good DX prioritizes ease of use, efficiency, and productivity, and can lead to faster development times, higher quality code, and greater developer satisfaction. Factors that can impact DX include documentation, community support, testing tools, and integration with other systems. As TypeScript usage continues to grow and gains more prominence in the ecosystem, enhancing its support is essential for delivering an improved developer experience for newcomers and experienced users alike. ## Package management The ability to easily install and manage dependencies and development tools is a key part of the user experience, and for that reason Node.js must provide a package manager as part of its distribution. Node.js includes `npm` for this purpose. This is for historical reasons — when `npm` was added in 2011, it was the only JavaScript package manager — and because it is the reference implementation for the npm registry, which is the de facto primary source for most JavaScript software. In accordance with our [policy][distribution-policy] of not including multiple dependencies or tools that serve the same purpose, the Node.js project does not include any other package managers; though it may include other software to download other package managers. [distribution-policy]: ./distribution.md	8.25 KB	2025-02-28 19:16
📄 technical-values.md # Technical values and their priorities The project uses these technical values to establish priorities and guide collaboration. These are the shared values as of this writing and will evolve. We hope they are useful to people new to the project in order to better understand which contributions will be aligned with the current direction and as thinking points when trading off between conflicting goals. The factors influencing every discussion/decision are different and priority 1 does not always trump priority 2 and so on. ## Values and priority level * Priority 1 - Developer experience * Priority 2 - Stability * Priority 3 - Operational qualities * Priority 4 - Node.js maintainer experience * Priority 5 - Up to date technology and APIs ## Value descriptions ### 1 - Developer experience We value ensuring that developers are productive and enjoy developing with Node.js. Some key elements of this include: * Approachability (both technical and community) * Great documentation * Bundling friction-reducing APIs and components, even though they could be provided externally * Compatibility and interoperability with browsers and other JavaScript environments so that as much code as possible runs as is both in Node.js and in the other environments * Enabling/supporting external packages to ensure overall developer experience ### 2 - Stability Whenever possible, we seek to ensure that working code continues to work. To keep the trust of developers and users, we value stability. Some key elements of this include: * Backward compatibility * Stable releases on a predictable schedule * A strong safety net, including testing how changes in Node.js affect popular packages * Careful consideration of what goes into Long Term Support (LTS) releases ### 3 - Operational qualities We value keeping Node.js safe, performant, and lightweight. We value enabling the ability to investigate and debug problems in development and production. Some key elements of this include: * High throughput (speed) * Fast startup * Small binary size * Small memory footprint * High-quality debugging tools * Robust diagnostic tools (profilers, etc.) * Responsible security practices ### 4 - Node.js maintainer experience We value the productivity and happiness of the Node.js maintainers. Some key elements of this include: * Approachability of the codebase * Good internal documentation and guides * Low-friction policies and processes * Good CI and tooling to make maintainers productive ### 5 - Up to date technology and APIs We value providing developers with modern APIs and technologies following existing standards whenever possible. Some key elements of this include: * Participating in standards work and organizations * Web API compatibility * Supporting and exposing new technologies and standards through early adoption	2.79 KB	2025-02-28 19:16
📄 using-internal-errors.md # Using the internal/errors.js module ## What is internal/errors.js The `require('internal/errors')` module is an internal-only module that can be used to produce `Error`, `TypeError` and `RangeError` instances that use a static, permanent error code and an optionally parameterized message. The intent of the module is to allow errors provided by Node.js to be assigned a permanent identifier. Without a permanent identifier, userland code may need to inspect error messages to distinguish one error from another. An unfortunate result of that practice is that changes to error messages result in broken code in the ecosystem. For that reason, Node.js has considered error message changes to be breaking changes. By providing a permanent identifier for a specific error, we reduce the need for userland code to inspect error messages. Switching an existing error to use the `internal/errors` module must be considered a `semver-major` change. ## Using internal/errors.js The `internal/errors` module exposes all custom errors as subclasses of the builtin errors. After being added, an error can be found in the `codes` object. For instance, an existing `Error` such as: ```js const err = new TypeError(`Expected string received ${type}`); ``` Can be replaced by first adding a new error key into the `internal/errors.js` file: ```js E('FOO', 'Expected string received %s', TypeError); ``` Then replacing the existing `new TypeError` in the code: ```js const { FOO } = require('internal/errors').codes; // ... const err = new FOO(type); ``` ## Adding new errors New static error codes are added by modifying the `internal/errors.js` file and appending the new error codes to the end using the utility `E()` method. ```js E('EXAMPLE_KEY1', 'This is the error value', TypeError); E('EXAMPLE_KEY2', (a, b) => `${a} ${b}`, RangeError); ``` The first argument passed to `E()` is the static identifier. The second argument is either a String with optional `util.format()` style replacement tags (e.g. `%s`, `%d`), or a function returning a String. The optional additional arguments passed to the `errors.message()` function (which is used by the `errors.Error`, `errors.TypeError` and `errors.RangeError` classes), will be used to format the error message. The third argument is the base class that the new error will extend. It is possible to create multiple derived classes by providing additional arguments. The other ones will be exposed as properties of the main class: <!-- eslint-disable no-unreachable --> ```js E('EXAMPLE_KEY', 'Error message', TypeError, RangeError); // In another module const { EXAMPLE_KEY } = require('internal/errors').codes; // TypeError throw new EXAMPLE_KEY(); // RangeError throw new EXAMPLE_KEY.RangeError(); ``` ## Documenting new errors Whenever a new static error code is added and used, corresponding documentation for the error code should be added to the `doc/api/errors.md` file. This will give users a place to go to easily look up the meaning of individual error codes. In case `make lint` fails to detect the new error codes added into `errors.md`, the markdown linting cache must be cleaned with `make lint-md-clean`. ## Testing new errors When adding a new error, corresponding test(s) for the error message formatting may also be required. If the message for the error is a constant string then no test is required for the error message formatting as we can trust the error helper implementation. An example of this kind of error would be: ```js E('ERR_SOCKET_ALREADY_BOUND', 'Socket is already bound'); ``` If the error message is not a constant string then tests to validate the formatting of the message based on the parameters used when creating the error should be added to `test/parallel/test-internal-errors.js`. These tests should validate all of the different ways parameters can be used to generate the final message string. A simple example is: ```js // Test ERR_TLS_CERT_ALTNAME_INVALID assert.strictEqual( errors.message('ERR_TLS_CERT_ALTNAME_INVALID', ['altname']), 'Hostname/IP does not match certificate\'s altnames: altname'); ``` In addition, there should also be tests which validate the use of the error based on where it is used in the codebase. If the error message is static, these tests should only validate that the expected code is received and NOT validate the message. This will reduce the amount of test change required when the message for an error changes. ```js assert.throws(() => { socket.bind(); }, common.expectsError({ code: 'ERR_SOCKET_ALREADY_BOUND', type: Error, })); ``` Avoid changing the format of the message after the error has been created. If it does make sense to do this for some reason, then additional tests validating the formatting of the error message for those cases will likely be required. ## API ### Object: errors.codes Exposes all internal error classes to be used by Node.js APIs. ### Method: errors.message(key, args) * `key` {string} The static error identifier * `args` {Array} Zero or more optional arguments passed as an Array * Returns: {string} Returns the formatted error message string for the given `key`.	5.05 KB	2025-02-28 19:16
📄 using-symbols.md # Using global symbols ES6 introduced a new type: `Symbol`. This new type is _immutable_, and it is often used for metaprogramming purposes, as it can be used as property keys like string. There are two types of symbols, local and global. Symbol-keyed properties of an object are not included in the output of `JSON.stringify()`, but the `util.inspect()` function includes them by default. Learn more about symbols at <https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Symbol>. ## `Symbol(string)` Symbols created via `Symbol(string)` are local to the caller function. For this reason, we often use them to simulate private fields, like so: ```js const kField = Symbol('kField'); console.log(kField === Symbol('kField')); // false class MyObject { constructor() { this[kField] = 'something'; } } module.exports.MyObject = MyObject; ``` Symbols are not fully private, as the data could be accessed anyway: ```js for (const s of Object.getOwnPropertySymbols(obj)) { const desc = s.toString().replace(/Symbol$(.*)$$/, '$1'); if (desc === 'kField') { console.log(obj[s]); // 'something' } } ``` Local symbols make it harder for developers to monkey patch/access private fields, as they require more work than a property prefixed with an `_`. Monkey patching private API that were not designed to be monkey-patchable make maintaining and evolving Node.js harder, as private properties are not documented and can change within a patch release. Some extremely popular modules in the ecosystem monkey patch some internals, making it impossible for us to update and improve those areas without causing issues for a significant amount of users. ## `Symbol.for(string)` Symbols created with `Symbol.for(string)` are global and unique to the same V8 Isolate. On the first call to `Symbol.for(string)` a symbol is stored in a global registry and easily retrieved for every call of `Symbol.for(string)`. However, this might cause problems when two module authors use the same symbol for different reasons. ```js const s = Symbol.for('hello'); console.log(s === Symbol.for('hello')); // true ``` In the Node.js runtime we prefix all our global symbols with `nodejs.`, e.g. `Symbol.for('nodejs.hello')`. Global symbols should be preferred when a developer-facing interface is needed to allow behavior customization, i.e., metaprogramming.	2.33 KB	2025-02-28 19:16
📄 writing-and-running-benchmarks.md # How to write and run benchmarks in Node.js core ## Table of contents * [Prerequisites](#prerequisites) * [HTTP benchmark requirements](#http-benchmark-requirements) * [HTTPS benchmark requirements](#https-benchmark-requirements) * [HTTP/2 benchmark requirements](#http2-benchmark-requirements) * [Benchmark analysis requirements](#benchmark-analysis-requirements) * [Running benchmarks](#running-benchmarks) * [Running individual benchmarks](#running-individual-benchmarks) * [Running all benchmarks](#running-all-benchmarks) * [Specifying CPU Cores for Benchmarks with run.js](#specifying-cpu-cores-for-benchmarks-with-runjs) * [Filtering benchmarks](#filtering-benchmarks) * [Comparing Node.js versions](#comparing-nodejs-versions) * [Comparing parameters](#comparing-parameters) * [Running benchmarks on the CI](#running-benchmarks-on-the-ci) * [Creating a benchmark](#creating-a-benchmark) * [Basics of a benchmark](#basics-of-a-benchmark) * [Creating an HTTP benchmark](#creating-an-http-benchmark) ## Prerequisites Basic Unix tools are required for some benchmarks. [Git for Windows][git-for-windows] includes Git Bash and the necessary tools, which need to be included in the global Windows `PATH`. ### HTTP benchmark requirements Most of the HTTP benchmarks require a benchmarker to be installed. This can be either [`wrk`][wrk] or [`autocannon`][autocannon]. `Autocannon` is a Node.js script that can be installed using `npm install -g autocannon`. It will use the Node.js executable that is in the path. In order to compare two HTTP benchmark runs, make sure that the Node.js version in the path is not altered. `wrk` may be available through one of the available package managers. If not, it can be easily built [from source][wrk] via `make`. By default, `wrk` will be used as the benchmarker. If it is not available, `autocannon` will be used in its place. When creating an HTTP benchmark, the benchmarker to be used should be specified by providing it as an argument: `node benchmark/run.js --set benchmarker=autocannon http` `node benchmark/http/simple.js benchmarker=autocannon` #### HTTPS benchmark requirements To run the `https` benchmarks, one of `autocannon` or `wrk` benchmarkers must be used. `node benchmark/https/simple.js benchmarker=autocannon` #### HTTP/2 benchmark requirements To run the `http2` benchmarks, the `h2load` benchmarker must be used. The `h2load` tool is a component of the `nghttp2` project and may be installed from [nghttp2.org][] or built from source. `node benchmark/http2/simple.js benchmarker=h2load` ### Benchmark analysis requirements To analyze the results statistically, you can use either the [node-benchmark-compare][] tool or the R script `benchmark/compare.R`. [node-benchmark-compare][] is a Node.js script that can be installed with `npm install -g node-benchmark-compare`. To draw comparison plots when analyzing the results, `R` must be installed. Use one of the available package managers or download it from <https://www.r-project.org/>. The R packages `ggplot2` and `plyr` are also used and can be installed using the R REPL. ```console $ R install.packages("ggplot2") install.packages("plyr") ``` If a message states that a CRAN mirror must be selected first, specify a mirror with the `repo` parameter. ```r install.packages("ggplot2", repo="http://cran.us.r-project.org") ``` Of course, use an appropriate mirror based on location. A list of mirrors is [located here](https://cran.r-project.org/mirrors.html). ## Running benchmarks ### Setting CPU Frequency scaling governor to "performance" It is recommended to set the CPU frequency to `performance` before running benchmarks. This increases the likelihood of each benchmark achieving peak performance according to the hardware. Therefore, run: ```console $ ./benchmarks/cpu.sh fast ``` ### Running individual benchmarks This can be useful for debugging a benchmark or doing a quick performance measure. But it does not provide the statistical information to make any conclusions about the performance. Individual benchmarks can be executed by simply executing the benchmark script with node. ```console $ node benchmark/buffers/buffer-tostring.js buffers/buffer-tostring.js n=10000000 len=0 arg=true: 62710590.393305704 buffers/buffer-tostring.js n=10000000 len=1 arg=true: 9178624.591787899 buffers/buffer-tostring.js n=10000000 len=64 arg=true: 7658962.8891432695 buffers/buffer-tostring.js n=10000000 len=1024 arg=true: 4136904.4060201733 buffers/buffer-tostring.js n=10000000 len=0 arg=false: 22974354.231509723 buffers/buffer-tostring.js n=10000000 len=1 arg=false: 11485945.656765845 buffers/buffer-tostring.js n=10000000 len=64 arg=false: 8718280.70650129 buffers/buffer-tostring.js n=10000000 len=1024 arg=false: 4103857.0726124765 ``` Each line represents a single benchmark with parameters specified as `${variable}=${value}`. Each configuration combination is executed in a separate process. This ensures that benchmark results aren't affected by the execution order due to V8 optimizations. The last number is the rate of operations measured in ops/sec (higher is better). Furthermore a subset of the configurations can be specified, by setting them in the process arguments: ```console $ node benchmark/buffers/buffer-tostring.js len=1024 buffers/buffer-tostring.js n=10000000 len=1024 arg=true: 3498295.68561504 buffers/buffer-tostring.js n=10000000 len=1024 arg=false: 3783071.1678948295 ``` ### Running all benchmarks Similar to running individual benchmarks, a group of benchmarks can be executed by using the `run.js` tool. To see how to use this script, run `node benchmark/run.js`. Again this does not provide the statistical information to make any conclusions. ```console $ node benchmark/run.js assert assert/deepequal-buffer.js assert/deepequal-buffer.js method="deepEqual" strict=0 len=100 n=20000: 773,200.4995493788 assert/deepequal-buffer.js method="notDeepEqual" strict=0 len=100 n=20000: 964,411.712953848 ... assert/deepequal-map.js assert/deepequal-map.js method="deepEqual_primitiveOnly" strict=0 len=500 n=500: 20,445.06368453332 assert/deepequal-map.js method="deepEqual_objectOnly" strict=0 len=500 n=500: 1,393.3481642240833 ... assert/deepequal-object.js assert/deepequal-object.js method="deepEqual" strict=0 size=100 n=5000: 1,053.1950937538475 assert/deepequal-object.js method="notDeepEqual" strict=0 size=100 n=5000: 9,734.193251965213 ... ``` It is possible to execute more groups by adding extra process arguments. ```bash node benchmark/run.js assert async_hooks ``` It's also possible to execute the benchmark more than once using the `--runs` flag. ```bash node benchmark/run.js --runs 10 assert async_hooks ``` This command will run the benchmark files in `benchmark/assert` and `benchmark/async_hooks` 10 times each. #### Specifying CPU Cores for Benchmarks with run.js When using `run.js` to execute a group of benchmarks, you can specify on which CPU cores the benchmarks should execute by using the `--set CPUSET=value` option. This controls the CPU core affinity for the benchmark process, potentially reducing interference from other processes and allowing for performance testing under specific hardware configurations. The `CPUSET` option utilizes the `taskset` command's format for setting CPU affinity, where `value` can be a single core number or a range of cores. Examples: * `node benchmark/run.js --set CPUSET=0` ... runs benchmarks on CPU core 0. * `node benchmark/run.js --set CPUSET=0-2` ... specifies that benchmarks should run on CPU cores 0 to 2. Note: This option is only applicable when using `run.js`. Ensure the `taskset` command is available on your system and the specified `CPUSET` format matches its requirements. #### Filtering benchmarks `benchmark/run.js` and `benchmark/compare.js` have `--filter pattern` and `--exclude pattern` options, which can be used to run a subset of benchmarks or to exclude specific benchmarks from the execution, respectively. ```console $ node benchmark/run.js --filter "deepequal-b" assert assert/deepequal-buffer.js assert/deepequal-buffer.js method="deepEqual" strict=0 len=100 n=20000: 773,200.4995493788 assert/deepequal-buffer.js method="notDeepEqual" strict=0 len=100 n=20000: 964,411.712953848 $ node benchmark/run.js --exclude "deepequal-b" assert assert/deepequal-map.js assert/deepequal-map.js method="deepEqual_primitiveOnly" strict=0 len=500 n=500: 20,445.06368453332 assert/deepequal-map.js method="deepEqual_objectOnly" strict=0 len=500 n=500: 1,393.3481642240833 ... assert/deepequal-object.js assert/deepequal-object.js method="deepEqual" strict=0 size=100 n=5000: 1,053.1950937538475 assert/deepequal-object.js method="notDeepEqual" strict=0 size=100 n=5000: 9,734.193251965213 ... ``` `--filter` and `--exclude` can be repeated to provide multiple patterns. ```console $ node benchmark/run.js --filter "deepequal-b" --filter "deepequal-m" assert assert/deepequal-buffer.js assert/deepequal-buffer.js method="deepEqual" strict=0 len=100 n=20000: 773,200.4995493788 assert/deepequal-buffer.js method="notDeepEqual" strict=0 len=100 n=20000: 964,411.712953848 assert/deepequal-map.js assert/deepequal-map.js method="deepEqual_primitiveOnly" strict=0 len=500 n=500: 20,445.06368453332 assert/deepequal-map.js method="deepEqual_objectOnly" strict=0 len=500 n=500: 1,393.3481642240833 $ node benchmark/run.js --exclude "deepequal-b" --exclude "deepequal-m" assert assert/deepequal-object.js assert/deepequal-object.js method="deepEqual" strict=0 size=100 n=5000: 1,053.1950937538475 assert/deepequal-object.js method="notDeepEqual" strict=0 size=100 n=5000: 9,734.193251965213 ... assert/deepequal-prims-and-objs-big-array-set.js assert/deepequal-prims-and-objs-big-array-set.js method="deepEqual_Array" strict=0 len=20000 n=25 primitive="string": 865.2977195251661 assert/deepequal-prims-and-objs-big-array-set.js method="notDeepEqual_Array" strict=0 len=20000 n=25 primitive="string": 827.8297281403861 assert/deepequal-prims-and-objs-big-array-set.js method="deepEqual_Set" strict=0 len=20000 n=25 primitive="string": 28,826.618268696366 ... ``` If `--filter` and `--exclude` are used together, `--filter` is applied first, and `--exclude` is applied on the result of `--filter`: ```console $ node benchmark/run.js --filter "bench-" process process/bench-env.js process/bench-env.js operation="get" n=1000000: 2,356,946.0770617095 process/bench-env.js operation="set" n=1000000: 1,295,176.3266261867 process/bench-env.js operation="enumerate" n=1000000: 24,592.32231990992 process/bench-env.js operation="query" n=1000000: 3,625,787.2150573144 process/bench-env.js operation="delete" n=1000000: 1,521,131.5742806569 process/bench-hrtime.js process/bench-hrtime.js type="raw" n=1000000: 13,178,002.113936031 process/bench-hrtime.js type="diff" n=1000000: 11,585,435.712423025 process/bench-hrtime.js type="bigint" n=1000000: 13,342,884.703919787 $ node benchmark/run.js --filter "bench-" --exclude "hrtime" process process/bench-env.js process/bench-env.js operation="get" n=1000000: 2,356,946.0770617095 process/bench-env.js operation="set" n=1000000: 1,295,176.3266261867 process/bench-env.js operation="enumerate" n=1000000: 24,592.32231990992 process/bench-env.js operation="query" n=1000000: 3,625,787.2150573144 process/bench-env.js operation="delete" n=1000000: 1,521,131.5742806569 ``` #### Grouping benchmarks Benchmarks can also have groups, giving the developer greater flexibility in differentiating between test cases and also helping reduce the time to run the combination of benchmark parameters. By default, all groups are executed when running the benchmark. However, it is possible to specify individual groups by setting the `NODE_RUN_BENCHMARK_GROUPS` environment variable when running `compare.js`: ```bash NODE_RUN_BENCHMARK_GROUPS=fewHeaders,manyHeaders node http/headers.js ``` ### Comparing Node.js versions To compare the effect of a new Node.js version use the `compare.js` tool. This will run each benchmark multiple times, making it possible to calculate statistics on the performance measures. To see how to use this script, run `node benchmark/compare.js`. As an example on how to check for a possible performance improvement, the [#5134](https://github.com/nodejs/node/pull/5134) pull request will be used as an example. This pull request _claims_ to improve the performance of the `node:string_decoder` module. First build two versions of Node.js, one from the `main` branch (here called `./node-main`) and another with the pull request applied (here called `./node-pr-5134`). To run multiple compiled versions in parallel you need to copy the output of the build: `cp ./out/Release/node ./node-main`. Check out the following example: ```bash git checkout main ./configure && make -j4 cp ./out/Release/node ./node-main git checkout pr-5134 ./configure && make -j4 cp ./out/Release/node ./node-pr-5134 ``` The `compare.js` tool will then produce a csv file with the benchmark results. ```bash node benchmark/compare.js --old ./node-main --new ./node-pr-5134 string_decoder > compare-pr-5134.csv ``` _Tips: there are some useful options of `benchmark/compare.js`. For example, if you want to compare the benchmark of a single script instead of a whole module, you can use the `--filter` option:_ ```console --new ./new-node-binary new node binary (required) --old ./old-node-binary old node binary (required) --runs 30 number of samples --filter pattern string to filter benchmark scripts --exclude pattern excludes scripts matching <pattern> (can be repeated) --set variable=value set benchmark variable (can be repeated) --no-progress don't show benchmark progress indicator Examples: --set CPUSET=0 Runs benchmarks on CPU core 0. --set CPUSET=0-2 Specifies that benchmarks should run on CPU cores 0 to 2. Note: The CPUSET format should match the specifications of the 'taskset' command ``` For analyzing the benchmark results, use [node-benchmark-compare][] or the R scripts: * `benchmark/compare.R` * `benchmark/bar.R` ```console $ node-benchmark-compare compare-pr-5134.csv # or cat compare-pr-5134.csv \| Rscript benchmark/compare.R confidence improvement accuracy () () () string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=128 encoding='ascii' * -3.76 % ±1.36% ±1.82% ±2.40% string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=128 encoding='utf8' -0.81 % ±0.53% ±0.71% ±0.93% string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=32 encoding='ascii' * -2.70 % ±0.83% ±1.11% ±1.45% string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=32 encoding='base64-ascii' *** -1.57 % ±0.83% ±1.11% ±1.46% ... ``` In the output, _improvement_ is the relative improvement of the new version, hopefully this is positive. _confidence_ tells if there is enough statistical evidence to validate the _improvement_. If there is enough evidence then there will be at least one star (``), more stars is just better. However if there are no stars, then don't make any conclusions based on the _improvement_.* Sometimes this is fine, for example if no improvements are expected, then there shouldn't be any stars. A word of caution: Statistics is not a foolproof tool. If a benchmark shows a statistical significant difference, there is a 5% risk that this difference doesn't actually exist. For a single benchmark this is not an issue. But when considering 20 benchmarks it's normal that one of them will show significance, when it shouldn't. A possible solution is to instead consider at least two stars (``) as the threshold, in that case the risk is 1%. If three stars (``) is considered the risk is 0.1%. However this may require more runs to obtain (can be set with `--runs`). _For the statistically minded, the script performs an [independent/unpaired 2-group t-test][t-test], with the null hypothesis that the performance is the same for both versions. The confidence field will show a star if the p-value is less than `0.05`._ The `compare.R` tool can additionally produce a box plot by using the `--plot filename` option. In this case there are 48 different benchmark combinations, and there may be a need to filter the csv file. This can be done while benchmarking using the `--set` parameter (e.g. `--set encoding=ascii`) or by filtering results afterwards using tools such as `sed` or `grep`. In the `sed` case be sure to keep the first line since that contains the header information. ```console $ cat compare-pr-5134.csv \| sed '1p;/encoding='"'"ascii"'"'/!d' \| Rscript benchmark/compare.R --plot compare-plot.png confidence improvement accuracy () () () string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=128 encoding='ascii' -3.76 % ±1.36% ±1.82% ±2.40% string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=32 encoding='ascii' * -2.70 % ±0.83% ±1.11% ±1.45% string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=4096 encoding='ascii' * -4.06 % ±0.31% ±0.41% ±0.54% string_decoder/string-decoder.js n=2500000 chunkLen=256 inLen=1024 encoding='ascii' * -1.42 % ±0.58% ±0.77% ±1.01% ... ``` ![compare tool boxplot](doc_img/compare-boxplot.png) ### Comparing parameters It can be useful to compare the performance for different parameters, for example to analyze the time complexity. To do this use the `scatter.js` tool, this will run a benchmark multiple times and generate a csv with the results. To see how to use this script, run `node benchmark/scatter.js`. ```bash node benchmark/scatter.js benchmark/string_decoder/string-decoder.js > scatter.csv ``` After generating the csv, a comparison table can be created using the `scatter.R` tool. Even more useful it creates an actual scatter plot when using the `--plot filename` option. ```console $ cat scatter.csv \| Rscript benchmark/scatter.R --xaxis chunkLen --category encoding --plot scatter-plot.png --log aggregating variable: inLen chunkLen encoding rate confidence.interval 16 ascii 1515855.1 334492.68 16 base64-ascii 403527.2 89677.70 16 base64-utf8 322352.8 70792.93 16 utf16le 1714567.5 388439.81 16 utf8 1100181.6 254141.32 64 ascii 3550402.0 661277.65 64 base64-ascii 1093660.3 229976.34 64 base64-utf8 997804.8 227238.04 64 utf16le 3372234.0 647274.88 64 utf8 1731941.2 360854.04 256 ascii 5033793.9 723354.30 256 base64-ascii 1447962.1 236625.96 256 base64-utf8 1357269.2 231045.70 256 utf16le 4039581.5 655483.16 256 utf8 1828672.9 360311.55 1024 ascii 5677592.7 624771.56 1024 base64-ascii 1494171.7 227302.34 1024 base64-utf8 1399218.9 224584.79 1024 utf16le 4157452.0 630416.28 1024 utf8 1824266.6 359628.52 ``` Because the scatter plot can only show two variables (in this case _chunkLen_ and _encoding_) the rest is aggregated. Sometimes aggregating is a problem, this can be solved by filtering. This can be done while benchmarking using the `--set` parameter (e.g. `--set encoding=ascii`) or by filtering results afterwards using tools such as `sed` or `grep`. In the `sed` case be sure to keep the first line since that contains the header information. ```console $ cat scatter.csv \| sed -E '1p;/([^,]+, ){3}128,/!d' \| Rscript benchmark/scatter.R --xaxis chunkLen --category encoding --plot scatter-plot.png --log chunkLen encoding rate confidence.interval 16 ascii 1302078.5 71692.27 16 base64-ascii 338669.1 15159.54 16 base64-utf8 281904.2 20326.75 16 utf16le 1381515.5 58533.61 16 utf8 831183.2 33631.01 64 ascii 4363402.8 224030.00 64 base64-ascii 1036825.9 48644.72 64 base64-utf8 780059.3 60994.98 64 utf16le 3900749.5 158366.84 64 utf8 1723710.6 80665.65 256 ascii 8472896.1 511822.51 256 base64-ascii 2215884.6 104347.53 256 base64-utf8 1996230.3 131778.47 256 utf16le 5824147.6 234550.82 256 utf8 2019428.8 100913.36 1024 ascii 8340189.4 598855.08 1024 base64-ascii 2201316.2 111777.68 1024 base64-utf8 2002272.9 128843.11 1024 utf16le 5789281.7 240642.77 1024 utf8 2025551.2 81770.69 ``` ![compare tool boxplot](doc_img/scatter-plot.png) ### Running benchmarks on the CI To see the performance impact of a pull request by running benchmarks on the CI, check out [How to: Running core benchmarks on Node.js CI][benchmark-ci]. ## Creating a benchmark ### Basics of a benchmark All benchmarks use the `require('../common.js')` module. This contains the `createBenchmark(main, configs[, options])` method which will setup the benchmark. The arguments of `createBenchmark` are: * `main` {Function} The benchmark function, where the code running operations and controlling timers should go * `configs` {Object} The benchmark parameters. `createBenchmark` will run all possible combinations of these parameters, unless specified otherwise. Each configuration is a property with an array of possible values. The configuration values can only be strings or numbers. * `options` {Object} The benchmark options. Supported options: * `flags` {Array} Contains node-specific command line flags to pass to the child process. * `byGroups` {Boolean} option for processing `configs` by groups: ```js const bench = common.createBenchmark(main, { groupA: { source: ['array'], len: [10, 2048], n: [50], }, groupB: { source: ['buffer', 'string'], len: [2048], n: [50, 2048], }, }, { byGroups: true }); ``` * `combinationFilter` {Function} Has a single parameter which is an object containing a combination of benchmark parameters. It should return `true` or `false` to indicate whether the combination should be included or not. `createBenchmark` returns a `bench` object, which is used for timing the runtime of the benchmark. Run `bench.start()` after the initialization and `bench.end(n)` when the benchmark is done. `n` is the number of operations performed in the benchmark. The benchmark script will be run twice: The first pass will configure the benchmark with the combination of parameters specified in `configs`, and WILL NOT run the `main` function. In this pass, no flags except the ones directly passed via commands when running the benchmarks will be used. In the second pass, the `main` function will be run, and the process will be launched with: * The flags passed into `createBenchmark` (the third argument) * The flags in the command passed when the benchmark was run Beware that any code outside the `main` function will be run twice in different processes. This could be troublesome if the code outside the `main` function has side effects. In general, prefer putting the code inside the `main` function if it's more than just declaration. ```js 'use strict'; const common = require('../common.js'); const { SlowBuffer } = require('node:buffer'); const configs = { // Number of operations, specified here so they show up in the report. // Most benchmarks just use one value for all runs. n: [1024], type: ['fast', 'slow'], // Custom configurations size: [16, 128, 1024], // Custom configurations }; const options = { // Add --expose-internals in order to require internal modules in main flags: ['--zero-fill-buffers'], }; // `main` and `configs` are required, `options` is optional. const bench = common.createBenchmark(main, configs, options); // Any code outside main will be run twice, // in different processes, with different command line arguments. function main(conf) { // Only flags that have been passed to createBenchmark // earlier when main is run will be in effect. // In order to benchmark the internal modules, require them here. For example: // const URL = require('internal/url').URL // Start the timer bench.start(); // Do operations here const BufferConstructor = conf.type === 'fast' ? Buffer : SlowBuffer; for (let i = 0; i < conf.n; i++) { new BufferConstructor(conf.size); } // End the timer, pass in the number of operations bench.end(conf.n); } ``` ### Creating an HTTP benchmark The `bench` object returned by `createBenchmark` implements `http(options, callback)` method. It can be used to run external tool to benchmark HTTP servers. ```js 'use strict'; const common = require('../common.js'); const bench = common.createBenchmark(main, { kb: [64, 128, 256, 1024], connections: [100, 500], duration: 5, }); function main(conf) { const http = require('node:http'); const len = conf.kb * 1024; const chunk = Buffer.alloc(len, 'x'); const server = http.createServer((req, res) => { res.end(chunk); }); server.listen(common.PORT, () => { bench.http({ connections: conf.connections, }, () => { server.close(); }); }); } ``` Supported options keys are: * `port` - defaults to `common.PORT` * `path` - defaults to `/` * `connections` - number of concurrent connections to use, defaults to 100 * `duration` - duration of the benchmark in seconds, defaults to 10 * `benchmarker` - benchmarker to use, defaults to the first available http benchmarker [autocannon]: https://github.com/mcollina/autocannon [benchmark-ci]: https://github.com/nodejs/benchmarking/blob/HEAD/docs/core_benchmarks.md [git-for-windows]: https://git-scm.com/download/win [nghttp2.org]: https://nghttp2.org [node-benchmark-compare]: https://github.com/targos/node-benchmark-compare [t-test]: https://en.wikipedia.org/wiki/Student%27s_t-test#Equal_or_unequal_sample_sizes%2C_unequal_variances_%28sX1_%3E_2sX2_or_sX2_%3E_2sX1%29 [wrk]: https://github.com/wg/wrk	26.27 KB	2025-02-28 19:16
📄 writing-tests.md # How to write a test for the Node.js project ## What is a test? Most tests in Node.js core are JavaScript programs that exercise a functionality provided by Node.js and check that it behaves as expected. Tests should exit with code `0` on success. A test will fail if: * It exits by setting `process.exitCode` to a non-zero number. * This is usually done by having an assertion throw an uncaught Error. * Occasionally, using `process.exit(code)` may be appropriate. * It never exits. In this case, the test runner will terminate the test because it sets a maximum time limit. Add tests when: * Adding new functionality. * Fixing regressions and bugs. * Expanding test coverage. ## Test directory structure See [directory structure overview][] for outline of existing test and locations. When deciding on whether to expand an existing test file or create a new one, consider going through the files related to the subsystem. For example, look for `test-streams` when writing a test for `lib/streams.js`. ## Test structure Let's analyze this basic test from the Node.js test suite: ```js 'use strict'; // 1 const common = require('../common'); // 2 const fixtures = require('../common/fixtures'); // 3 // This test ensures that the http-parser can handle UTF-8 characters // 5 // in the http header. // 6 const assert = require('node:assert'); // 8 const http = require('node:http'); // 9 const server = http.createServer(common.mustCall((req, res) => { // 11 res.end('ok'); // 12 })); // 13 server.listen(0, () => { // 14 http.get({ // 15 port: server.address().port, // 16 headers: { 'Test': 'Düsseldorf' }, // 17 }, common.mustCall((res) => { // 18 assert.strictEqual(res.statusCode, 200); // 19 server.close(); // 20 })); // 21 }); // 22 // ... // 23 ``` ### Lines 1-3 ```js 'use strict'; const common = require('../common'); const fixtures = require('../common/fixtures'); ``` The first line enables strict mode. All tests should be in strict mode unless the nature of the test requires that the test run without it. The second line loads the `common` module. The [`common` module][] is a helper module that provides useful tools for the tests. Some common functionality has been extracted into submodules, which are required separately like the fixtures module here. Even if a test uses no functions or other properties exported by `common`, the test should still include the `common` module before any other modules. This is because the `common` module includes code that will cause a test to fail if the test leaks variables into the global space. In situations where a test uses no functions or other properties exported by `common`, include it without assigning it to an identifier: ```js require('../common'); ``` ### Lines 5-6 ```js // This test ensures that the http-parser can handle UTF-8 characters // in the http header. ``` A test should start with a comment containing a brief description of what it is designed to test. ### Lines 8-9 ```js const assert = require('node:assert'); const http = require('node:http'); ``` The test checks functionality in the `node:http` module. Most tests use the `node:assert` module to confirm expectations of the test. The require statements are sorted in [ASCII][] order (digits, upper case, `_`, lower case). ### Lines 11-22 ```js const server = http.createServer(common.mustCall((req, res) => { res.end('ok'); })); server.listen(0, () => { http.get({ port: server.address().port, headers: { 'Test': 'Düsseldorf' }, }, common.mustCall((res) => { assert.strictEqual(res.statusCode, 200); server.close(); })); }); ``` This is the body of the test. This test is simple, it just tests that an HTTP server accepts `non-ASCII` characters in the headers of an incoming request. Interesting things to notice: * If the test doesn't depend on a specific port number, then always use 0 instead of an arbitrary value, as it allows tests to run in parallel safely, as the operating system will assign a random port. If the test requires a specific port, for example if the test checks that assigning a specific port works as expected, then it is ok to assign a specific port number. * The use of `common.mustCall` to check that some callbacks/listeners are called. * The HTTP server closes once all the checks have run. This way, the test can exit gracefully. Remember that for a test to succeed, it must exit with a status code of 0. ## General recommendations ### Timers Avoid timers unless the test is specifically testing timers. There are multiple reasons for this. Mainly, they are a source of flakiness. For a thorough explanation go [here](https://github.com/nodejs/testing/issues/27). In the event a test needs a timer, consider using the `common.platformTimeout()` method. It allows setting specific timeouts depending on the platform: ```js const timer = setTimeout(fail, common.platformTimeout(4000)); ``` will create a 4-second timeout on most platforms but a longer timeout on slower platforms. ### The _common_ API Make use of the helpers from the `common` module as much as possible. Please refer to the [common file documentation](https://github.com/nodejs/node/tree/HEAD/test/common) for the full details of the helpers. #### common.mustCall One interesting case is `common.mustCall`. The use of `common.mustCall` may avoid the use of extra variables and the corresponding assertions. Let's explain this with a real test from the test suite. ```js 'use strict'; require('../common'); const assert = require('node:assert'); const http = require('node:http'); let request = 0; let listening = 0; let response = 0; process.on('exit', () => { assert.equal(request, 1, 'http server "request" callback was not called'); assert.equal(listening, 1, 'http server "listening" callback was not called'); assert.equal(response, 1, 'http request "response" callback was not called'); }); const server = http.createServer((req, res) => { request++; res.end(); }).listen(0, () => { listening++; const options = { agent: null, port: server.address().port, }; http.get(options, (res) => { response++; res.resume(); server.close(); }); }); ``` This test could be greatly simplified by using `common.mustCall` like this: ```js 'use strict'; const common = require('../common'); const http = require('node:http'); const server = http.createServer(common.mustCall((req, res) => { res.end(); })).listen(0, common.mustCall(() => { const options = { agent: null, port: server.address().port, }; http.get(options, common.mustCall((res) => { res.resume(); server.close(); })); })); ``` Note: Many functions invoke their callback with an `err` value as the first argument. It is not a good idea to simply pass `common.mustCall()` to those because `common.mustCall()` will ignore the error. Use `common.mustSucceed()` instead. #### Countdown module The common [Countdown module](https://github.com/nodejs/node/tree/HEAD/test/common#countdown-module) provides a simple countdown mechanism for tests that require a particular action to be taken after a given number of completed tasks (for instance, shutting down an HTTP server after a specific number of requests). ```js const Countdown = require('../common/countdown'); const countdown = new Countdown(2, () => { console.log('.'); }); countdown.dec(); countdown.dec(); // The countdown callback will be invoked now. ``` #### Testing promises When writing tests involving promises, it is generally good to wrap the `onFulfilled` handler, otherwise the test could successfully finish if the promise never resolves (pending promises do not keep the event loop alive). Node.js automatically crashes - and hence, the test fails - in the case of an `unhandledRejection` event. ```js const common = require('../common'); const assert = require('node:assert'); const fs = require('node:fs').promises; // Wrap the `onFulfilled` handler in `common.mustCall()`. fs.readFile('test-file').then( common.mustCall( (content) => assert.strictEqual(content.toString(), 'test2'), )); ``` ### Flags Some tests will require running Node.js with specific command line flags set. To accomplish this, add a `// Flags:` comment in the preamble of the test followed by the flags. For example, to allow a test to require some of the `internal/` modules, add the `--expose-internals` flag. A test that would require `internal/freelist` could start like this: ```js 'use strict'; // Flags: --expose-internals require('../common'); const assert = require('node:assert'); const freelist = require('node:internal/freelist'); ``` In specific scenarios it may be useful to get a hold of `primordials` or `internalBinding()`. You can do so using ```bash node --expose-internals -r internal/test/binding lib/fs.js ``` This only works if you preload `node:internal/test/binding` by command line flag. ### Assertions When writing assertions, prefer the strict versions: `assert.strictEqual()` over `assert.equal()` * `assert.deepStrictEqual()` over `assert.deepEqual()` When using `assert.throws()`, if possible, provide the full error message: ```js assert.throws( () => { throw new Error('Wrong value'); }, /^Error: Wrong value$/, // Instead of something like /Wrong value/ ); ``` In the case of internal errors, prefer checking only the `code` property: ```js assert.throws( () => { throw new ERR_FS_FILE_TOO_LARGE(`${sizeKiB} Kb`); }, { code: 'ERR_FS_FILE_TOO_LARGE' }, // Do not include message: /^File size ([0-9]+ Kb) is greater than 2 GiB$/ ); ``` ### Console output Output written by tests to stdout or stderr, such as with `console.log()` or `console.error()`, can be useful when writing tests, as well as for debugging them during later maintenance. The output will be suppressed by the test runner (`./tools/test.py`) unless the test fails, but will always be displayed when running tests directly with `node`. For failing tests, the test runner will include the output along with the failed test assertion in the test report. Some output can help debugging by giving context to test failures. For example, when troubleshooting tests that timeout in CI. With no log statements, we have no idea where the test got hung up. There have been cases where tests fail without `console.log()`, and then pass when its added, so be cautious about its use, particularly in tests of the I/O and streaming APIs. Excessive use of console output is discouraged as it can overwhelm the display, including the Jenkins console and test report displays. Be particularly cautious of output in loops, or other contexts where output may be repeated many times in the case of failure. In some tests, it can be unclear whether a `console.log()` statement is required as part of the test (message tests, tests that check output from child processes, etc.), or is there as a debug aide. If there is any chance of confusion, use comments to make the purpose clear. ### ES.Next features For performance considerations, we only use a selected subset of ES.Next features in JavaScript code in the `lib` directory. However, when writing tests, for the ease of backporting, it is encouraged to use those ES.Next features that can be used directly without a flag in [all maintained branches][]. [node.green][] lists available features in each release, such as: * `let` and `const` over `var` * Template literals over string concatenation * Arrow functions when appropriate ## Naming test files Test files are named using kebab casing. The first component of the name is `test`. The second is the module or subsystem being tested. The third is usually the method or event name being tested. Subsequent components of the name add more information about what is being tested. For example, a test for the `beforeExit` event on the `process` object might be named `test-process-before-exit.js`. If the test specifically checked that arrow functions worked correctly with the `beforeExit` event, then it might be named `test-process-before-exit-arrow-functions.js`. ## Imported tests ### Web platform tests See [`test/wpt`](../../test/wpt/README.md) for more information. ## C++ unit test C++ code can be tested using [Google Test][]. Most features in Node.js can be tested using the methods described previously in this document. But there are cases where these might not be enough, for example writing code for Node.js that will only be called when Node.js is embedded. ### Adding a new test The unit test should be placed in `test/cctest` and be named with the prefix `test` followed by the name of unit being tested. For example, the code below would be placed in `test/cctest/test_env.cc`: ```cpp #include "gtest/gtest.h" #include "node_test_fixture.h" #include "env.h" #include "node.h" #include "v8.h" static bool called_cb = false; static void at_exit_callback(void* arg); class EnvTest : public NodeTestFixture { }; TEST_F(EnvTest, RunAtExit) { v8::HandleScope handle_scope(isolate_); v8::Local<v8::Context> context = v8::Context::New(isolate_); node::IsolateData* isolateData = node::CreateIsolateData(isolate_, uv_default_loop()); Argv argv{"node", "-e", ";"}; auto env = node::CreateEnvironment(isolateData, context, 1, argv, 2, argv); node::AtExit(env, at_exit_callback); node::RunAtExit(env); EXPECT_TRUE(called_cb); } static void at_exit_callback(void* arg) { called_cb = true; } ``` Next add the test to the `sources` in the `cctest` target in node.gyp: ```console 'sources': [ 'test/cctest/test_env.cc', ... ], ``` The only sources that should be included in the cctest target are actual test or helper source files. There might be a need to include specific object files that are compiled by the `node` target and this can be done by adding them to the `libraries` section in the cctest target. The test can be executed by running the `cctest` target: ```bash make cctest ``` A filter can be applied to run single/multiple test cases: ```bash make cctest GTEST_FILTER=EnvironmentTest.AtExitWithArgument ``` `cctest` can also be run directly which can be useful when debugging: ```bash out/Release/cctest --gtest_filter=EnvironmentTest.AtExit\* ``` ### Node.js test fixture There is a [test fixture][] named `node_test_fixture.h` which can be included by unit tests. The fixture takes care of setting up the Node.js environment and tearing it down after the tests have finished. It also contains a helper to create arguments to be passed into Node.js. It will depend on what is being tested if this is required or not. ### Test coverage To generate a test coverage report, see the [Test Coverage section of the Building guide][]. Nightly coverage reports for the Node.js `main` branch are available at <https://coverage.nodejs.org/>. [ASCII]: https://man7.org/linux/man-pages/man7/ascii.7.html [Google Test]: https://github.com/google/googletest [Test Coverage section of the Building guide]: https://github.com/nodejs/node/blob/HEAD/BUILDING.md#running-coverage [`common` module]: https://github.com/nodejs/node/blob/HEAD/test/common/README.md [all maintained branches]: https://github.com/nodejs/lts [directory structure overview]: https://github.com/nodejs/node/blob/HEAD/test/README.md#test-directories [node.green]: https://node.green/ [test fixture]: https://github.com/google/googletest/blob/HEAD/docs/primer.md#test-fixtures-using-the-same-data-configuration-for-multiple-tests-same-data-multiple-tests	16.03 KB	2025-02-28 19:16

Edit File:

Terminal