node-v16.13.2-linux-x64.tar.gz

<!--lint disable no-literal-urls--> <p align="center"> <a href="https://nodejs.org/"> <img alt="Node.js" src="https://nodejs.org/static/images/logo-light.svg" width="400" /> </a> </p> Node.js is an open-source, cross-platform, JavaScript runtime environment. It executes JavaScript code outside of a browser. For more information on using Node.js, see the [Node.js Website][]. The Node.js project uses an [open governance model](./GOVERNANCE.md). The [OpenJS Foundation][] provides support for the project. **This project is bound by a [Code of Conduct][].** # Table of contents * [Support](#support) * [Release types](#release-types) * [Download](#download) * [Current and LTS releases](#current-and-lts-releases) * [Nightly releases](#nightly-releases) * [API documentation](#api-documentation) * [Verifying binaries](#verifying-binaries) * [Building Node.js](#building-nodejs) * [Security](#security) * [Contributing to Node.js](#contributing-to-nodejs) * [Current project team members](#current-project-team-members) * [TSC (Technical Steering Committee)](#tsc-technical-steering-committee) * [Collaborators](#collaborators) * [Triagers](#triagers) * [Release keys](#release-keys) * [License](#license) ## Support Looking for help? Check out the [instructions for getting support](.github/SUPPORT.md). ## Release types * **Current**: Under active development. Code for the Current release is in the branch for its major version number (for example, [v15.x](https://github.com/nodejs/node/tree/v15.x)). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life of 8 months. Releases appearing each April convert to LTS (see below) each October. * **LTS**: Releases that receive Long Term Support, with a focus on stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 12 months of _Active LTS_ support and a further 18 months of _Maintenance_. LTS release lines have alphabetically-ordered code names, beginning with v4 Argon. There are no breaking changes or feature additions, except in some special circumstances. * **Nightly**: Code from the Current branch built every 24-hours when there are changes. Use with caution. Current and LTS releases follow [Semantic Versioning](https://semver.org). A member of the Release Team [signs](#release-keys) each Current and LTS release. For more information, see the [Release README](https://github.com/nodejs/Release#readme). ### Download Binaries, installers, and source tarballs are available at <https://nodejs.org/en/download/>. #### Current and LTS releases <https://nodejs.org/download/release/> The [latest](https://nodejs.org/download/release/latest/) directory is an alias for the latest Current release. The latest-_codename_ directory is an alias for the latest release from an LTS line. For example, the [latest-fermium](https://nodejs.org/download/release/latest-fermium/) directory contains the latest Fermium (Node.js 14) release. #### Nightly releases <https://nodejs.org/download/nightly/> Each directory name and filename contains a date (in UTC) and the commit SHA at the HEAD of the release. #### API documentation Documentation for the latest Current release is at <https://nodejs.org/api/>. Version-specific documentation is available in each release directory in the _docs_ subdirectory. Version-specific documentation is also at <https://nodejs.org/download/docs/>. ### Verifying binaries Download directories contain a `SHASUMS256.txt` file with SHA checksums for the files. To download `SHASUMS256.txt` using `curl`: ```console $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt ``` To check that a downloaded file matches the checksum, run it through `sha256sum` with a command such as: ```console $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c - ``` For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in `SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of `SHASUMS256.txt`. You will first need to import [the GPG keys of individuals authorized to create releases](#release-keys). To import the keys: ```console $ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D ``` See the bottom of this README for a full script to import active release keys. Next, download the `SHASUMS256.txt.sig` for the release: ```console $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig ``` Then use `gpg --verify SHASUMS256.txt.sig SHASUMS256.txt` to verify the file's signature. ## Building Node.js See [BUILDING.md](BUILDING.md) for instructions on how to build Node.js from source and a list of supported platforms. ## Security For information on reporting security vulnerabilities in Node.js, see [SECURITY.md](./SECURITY.md). ## Contributing to Node.js * [Contributing to the project][] * [Working Groups][] * [Strategic initiatives][] * [Technical values and prioritization][] ## Current project team members For information about the governance of the Node.js project, see [GOVERNANCE.md](./GOVERNANCE.md). <!-- node-core-utils depends on the format of the TSC list. If the format changes, those utilities need to be tested and updated. --> ### TSC (Technical Steering Committee) <!--lint disable prohibited-strings--> * [aduh95](https://github.com/aduh95) - **Antoine du Hamel** \<duhamelantoine1995@gmail.com> (he/him) * [apapirovski](https://github.com/apapirovski) - **Anatoli Papirovski** \<apapirovski@mac.com> (he/him) * [BethGriggs](https://github.com/BethGriggs) - **Beth Griggs** \<bgriggs@redhat.com> (she/her) * [BridgeAR](https://github.com/BridgeAR) - **Ruben Bridgewater** \<ruben@bridgewater.de> (he/him) * [ChALkeR](https://github.com/ChALkeR) - **Сковорода Никита Андреевич** \<chalkerx@gmail.com> (he/him) * [cjihrig](https://github.com/cjihrig) - **Colin Ihrig** \<cjihrig@gmail.com> (he/him) * [codebytere](https://github.com/codebytere) - **Shelley Vohr** \<shelley.vohr@gmail.com> (she/her) * [danielleadams](https://github.com/danielleadams) - **Danielle Adams** \<adamzdanielle@gmail.com> (she/her) * [fhinkel](https://github.com/fhinkel) - **Franziska Hinkelmann** \<franziska.hinkelmann@gmail.com> (she/her) * [gabrielschulhof](https://github.com/gabrielschulhof) - **Gabriel Schulhof** \<gabrielschulhof@gmail.com> * [gireeshpunathil](https://github.com/gireeshpunathil) - **Gireesh Punathil** \<gpunathi@in.ibm.com> (he/him) * [jasnell](https://github.com/jasnell) - **James M Snell** \<jasnell@gmail.com> (he/him) * [joyeecheung](https://github.com/joyeecheung) - **Joyee Cheung** \<joyeec9h3@gmail.com> (she/her) * [mcollina](https://github.com/mcollina) - **Matteo Collina** \<matteo.collina@gmail.com> (he/him) * [mhdawson](https://github.com/mhdawson) - **Michael Dawson** \<midawson@redhat.com> (he/him) * [mmarchini](https://github.com/mmarchini) - **Mary Marchini** \<oss@mmarchini.me> (she/her) * [MylesBorins](https://github.com/MylesBorins) - **Myles Borins** \<myles.borins@gmail.com> (he/him) * [richardlau](https://github.com/richardlau) - **Richard Lau** \<rlau@redhat.com> * [ronag](https://github.com/ronag) - **Robert Nagy** \<ronagy@icloud.com> * [targos](https://github.com/targos) - **Michaël Zasso** \<targos@protonmail.com> (he/him) * [tniessen](https://github.com/tniessen) - **Tobias Nießen** \<tniessen@tnie.de> (he/him) * [Trott](https://github.com/Trott) - **Rich Trott** \<rtrott@gmail.com> (he/him) <details> <summary>Emeriti</summary> ### TSC emeriti * [addaleax](https://github.com/addaleax) - **Anna Henningsen** \<anna@addaleax.net> (she/her) * [bnoordhuis](https://github.com/bnoordhuis) - **Ben Noordhuis** \<info@bnoordhuis.nl> * [chrisdickinson](https://github.com/chrisdickinson)