Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
dc609f5a81
node/deps/npm
History
npm CLI robot dad539f0c3
deps: upgrade npm to 10.8.0 
PR-URL: https://github.com/nodejs/node/pull/53014
Reviewed-By: Luke Karrys <luke@lukekarrys.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
2024-05-16 12:38:49 +00:00
..
bin deps: upgrade npm to 10.7.0 2024-05-01 06:53:22 +00:00
docs deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
lib deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
man deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
node_modules deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
tap-snapshots/test/lib deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
test deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
.npmrc
index.js
LICENSE
package.json deps: upgrade npm to 10.8.0 2024-05-16 12:38:49 +00:00
README.md

README.md

npm - a JavaScript package manager

npm version license CI - cli Benchmark Suite

Requirements

One of the following versions of Node.js must be installed to run npm:

  • 18.x.x >= 18.17.0
  • 20.5.0 or higher

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
  • Roadmap - Track & follow along with our public roadmap
  • Feedback - 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
  • Events Calendar - Keep track of our Open RFC calls, releases, meetups, conferences & more
  • Support - Experiencing problems with the npm website or registry? File a ticket here

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 here

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".