a package manager for JavaScript, report bugs and get support at:
Clone or download
Latest commit 59e5056 Aug 29, 2018
Failed to load latest commit information.
.github docs: replace troubleshooting.md with posts (#17) Jul 18, 2018
bin update-notifier: skip checking for updates in CI environments Aug 20, 2018
changelogs doc: Pull in changelogs from last npm@5 releases May 11, 2018
doc docs: Update republish time and lightly reorganize republish info (#48) Aug 20, 2018
html docs: use https when possible. (#7) Jul 23, 2018
lib pack: add dryRun option to packDirectory (#47) Aug 20, 2018
node_modules ci-info@1.4.0 Aug 22, 2018
scripts gen-changelog: fix npm.community url parsing Aug 22, 2018
test pack: add dryRun option to packDirectory (#47) Aug 20, 2018
.gitignore scripts: auto generate ignores Jun 8, 2018
.mailmap mailmap: Update with real names May 4, 2018
.npmignore misc: Exclude /.github directory from package (#20881) Jun 28, 2018
.npmrc Flatten dependencies and add dev deps to git May 24, 2018
.travis.yml travis: Add node v10 May 4, 2018
AUTHORS update AUTHORS Aug 23, 2018
CHANGELOG.md doc: update changelog for npm@6.4.1 Aug 23, 2018
CONTRIBUTING.md docs: replace troubleshooting.md with posts (#17) Jul 18, 2018
LICENSE license: fix npm public registry URL in notices Dec 4, 2015
Makefile makefile: call cache clean with --force May 4, 2018
README.md doc: Mention registry terms of use in manpage and registry doc (#54) Aug 20, 2018
appveyor.yml ci: add node 8 to appveyor.yml (#16935) Jun 5, 2017
configure Write builtin config with ./configure script Oct 8, 2011
make.bat Add a fake make file for Windows test-running love Oct 9, 2013
package-lock.json 6.4.1 Aug 29, 2018
package.json 6.4.1 Aug 29, 2018


npm(1) -- a JavaScript package manager

Build Status


This is just enough info to get you up and running.

Much more info will be available via npm help once it's installed.


You need node v6 or higher to run this program.

To install an old and unsupported version of npm that works on node v5 and prior, clone the git repo and dig through the old tags and branches.

npm is configured to use npm, Inc.'s public registry at https://registry.npmjs.org by default. Use of the npm public registry is subject to terms of use available at https://www.npmjs.com/policies/terms.

You can configure npm to use any compatible registry you like, and even run your own registry. Check out the doc on registries.

Super Easy Install

npm is bundled with node.

Windows Computers

Get the MSI. npm is in it.

Apple Macintosh Computers

Get the pkg. npm is in it.

Other Sorts of Unices

Run make install. npm will be installed with node.

If you want a more fancy pants install (a different version, customized paths, etc.) then read on.

Fancy Install (Unix)

There's a pretty robust install script at https://www.npmjs.com/install.sh. You can download that and run it.

Here's an example using curl:

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

Slightly Fancier

You can set any npm configuration params with that script:

npm_config_prefix=/some/path sh install.sh

Or, you can run it in uber-debuggery mode:

npm_debug=1 sh install.sh

Even Fancier

Get the code with git. Use make to build the docs and do other stuff. If you plan on hacking on npm, make link is your friend.

If you've got the npm source code, you can also semi-permanently set arbitrary config keys using the ./configure --key=val ..., and then run npm commands by doing node bin/npm-cli.js <command> <args>. (This is helpful for testing, or running stuff without actually installing npm itself.)

Windows Install or Upgrade

Many improvements for Windows users have been made in npm 3 - you will have a better experience if you run a recent version of npm. To upgrade, either use Microsoft's upgrade tool, download a new version of Node, or follow the Windows upgrade instructions in the Installing/upgrading npm post.

If that's not fancy enough for you, then you can fetch the code with git, and mess with it directly.

Installing on Cygwin



So sad to see you go.

sudo npm uninstall npm -g

Or, if that fails,

sudo make uninstall

More Severe Uninstalling

Usually, the above instructions are sufficient. That will remove npm, but leave behind anything you've installed.

If you would like to remove all the packages that you have installed, then you can use the npm ls command to find them, and then npm rm to remove them.

To remove cruft left behind by npm 0.x, you can use the included clean-old.sh script file. You can run it conveniently like this:

npm explore npm -g -- sh scripts/clean-old.sh

npm uses two configuration files, one for per-user configs, and another for global (every-user) configs. You can view them by doing:

npm config get userconfig   # defaults to ~/.npmrc
npm config get globalconfig # defaults to /usr/local/etc/npmrc

Uninstalling npm does not remove configuration files by default. You must remove them yourself manually if you want them gone. Note that this means that future npm installs will not remember the settings that you have chosen.

More Docs

Check out the docs.

You can use the npm help command to read any of them.

If you're a developer, and you want to use npm to publish your program, you should read this.


When you find issues, please report them:

Be sure to include all of the output from the npm command that didn't work as expected. The npm-debug.log file is also helpful to provide.

You can also find npm people in #npm on https://package.community/ or on Twitter. Whoever responds will no doubt tell you to put the output in a gist or email.


  • npm(1)
  • npm-help(1)
  • npm-index(7)