mirror of https://github.com/nodejs/node.git synced 2025-12-28 07:50:41 +00:00

History

npm CLI robot 0624e7a180 deps: upgrade npm to 11.7.0 PR-URL: https://github.com/nodejs/node/pull/61011 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>		2025-12-10 23:30:40 +00:00
..
bin	deps: upgrade npm to 11.6.0	2025-09-05 20:29:22 +00:00
docs	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
lib	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
man	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
node_modules	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
tap-snapshots	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
test	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
.npmrc
index.js
LICENSE
package.json	deps: upgrade npm to 11.7.0	2025-12-10 23:30:40 +00:00
README.md	deps: upgrade npm to 11.6.4	2025-11-27 20:46:00 +00:00

README.md

npm - a JavaScript package manager

Requirements

You should be running a currently supported version of Node.js to run npm. For a list of which versions of Node.js are currently supported, please see the Node.js releases page.

Installation

npm comes bundled with node, & most third-party distributions, by default. Officially supported downloads/distributions can be found at: nodejs.org/en/download

Direct Download

You can download & install npm directly from npmjs.com using our custom install.sh script:

curl -qL https://www.npmjs.com/install.sh | sh

Node Version Managers

If you're looking to manage multiple versions of Node.js &/or npm, consider using a node version manager

Usage

npm <command>

Links & Resources

Documentation - Official docs & how-tos for all things npm
- Note: you can also search docs locally with npm help-search <query>
Bug Tracker - Search or submit bugs against the CLI
Community Feedback and Discussions - Contribute ideas & discussion around the npm registry, website & CLI
RFCs - Contribute ideas & specifications for the API/design of the npm CLI
Service Status - Monitor the current status & see incident reports for the website & registry
Project Status - See the health of all our maintained OSS projects in one view
Support - Experiencing problems with the npm website or registry? File a ticket

Acknowledgments

npm is configured to use the npm Public Registry at https://registry.npmjs.org by default; Usage of this registry is subject to Terms of Use available at https://npmjs.com/policies/terms
You can configure npm to use any other compatible registry you prefer. You can read more about configuring third-party registries

FAQ on Branding

Is it "npm" or "NPM" or "Npm"?

npm should never be capitalized unless it is being displayed in a location that is customarily all-capitals (ex. titles on man pages).

Is "npm" an acronym for "Node Package Manager"?

Contrary to popular belief, npm is not in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for "npm is not an acronym" (if the project was named "ninaa", then it would be an acronym). The precursor to npm was actually a bash utility named "pm", which was the shortform name of "pkgmakeinst" - a bash function that installed various things on various platforms. If npm were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".