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

Much more info available vianpm help once it's installed.

You need node v0.8 or higher to run this program.

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

npm is bundled withnode.

Get the MSI. npm is in it.

Get the pkg. npm is in it.

Runmake install. npm will be installed with node.

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

There's a pretty robust install script athttps://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

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

Get the code with git. Usemake 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 setarbitrary config keys using the./configure --key=val ..., and thenrun npm commands by doingnode cli.js <cmd> <args>. (This is helpfulfor testing, or running stuff without actually installing npm itself.)

You can download a zip file fromhttps://github.com/npm/npm/releases, andunpack it in thenode_modules\npm\ folder inside node's installation folder.

To upgrade to npm 2, follow the Windows upgrade instructions inthe npm Troubleshooting Guide:

https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

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

No.

So sad to see you go.

sudo npm uninstall npm -g

Or, if that fails,

sudo make uninstall

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

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

To remove cruft left behind by npm 0.x, you can use the includedclean-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 anotherfor global (every-user) configs. You can view them by doing:

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

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

Although npm can be used programmatically, its API is meant for use by the CLIonly, and no guarantees are made regarding its fitness for any other purpose.If you want to use npm to reliably perform some task, the safest thing to do isto invoke the desirednpm command with appropriate arguments.

The semantic version of npm refers to the CLI itself, rather than theunderlying API.The internal API is not guaranteed to remain stable even whennpm's version indicates no breaking changes have been made according tosemver.

If youstill would like to use npm programmatically, it'spossible. The APIisn't very well documented, but itis rather simple.

Eventually, npm will be just a thin CLI wrapper around the modules that itdepends on, but for now, there are some things that only the CLI can do. Youshould try using one of npm's dependencies first, and only use the API if whatyou're trying to do is only supported by npm itself.

varnpm=require("npm")npm.load(myConfigObject,function(er){if(er)returnhandlError(er)npm.commands.install(["some","args"],function(er,data){if(er)returncommandFailed(er)// command succeeded, and data might have some info})npm.registry.log.on("log",function(message){ ....})})

Theload function takes an object hash of the command-line configs.The variousnpm.commands.<cmd> functions take anarray ofpositional argumentstrings. The last argument to anynpm.commands.<cmd> function is a callback. Some commands take otheroptional arguments. Read the source.

You cannot set configs individually for any single npm function at thistime. Sincenpm is a singleton, any call tonpm.config.set willchange the value forall npm commands in that process.

See./bin/npm-cli.js for an example of pulling config values off of thecommand line arguments using nopt. You may also want to check outnpm help config to learn about all the options you can set there.

Check out thedocs,especially thefaq.

You can use thenpm help command to read any of them.

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

"npm" and "The npm Registry" are owned by npm, Inc.All rights reserved. See the included LICENSE file for more details.

"Node.js" and "node" are trademarks owned by Joyent, Inc.

Modules published on the npm registry are not officially endorsed bynpm, Inc. or the Node.js project.

Data published to the npm registry is not part of npm itself, and isthe sole property of the publisher. While every effort is made toensure accountability, there is absolutely no guarantee, warranty, orassertion expressed or implied as to the quality, fitness for aspecific purpose, or lack of malice in any given npm package.

If you have a complaint about a package in the public npm registry,and cannotresolve it with the packageowner, please emailsupport@npmjs.com and explain the situation.

Any data published to The npm Registry (including user accountinformation) may be removed or modified at the sole discretion of thenpm server administrators.

npm is the property of npm, Inc.

If you publish something, it's yours, and you are solely accountablefor it.

If other people publish something, it's theirs.

Users can publish Bad Stuff. It will be removed promptly if reported.But there is no vetting process for published modules, and you usethem at your own risk. Please inspect the source.

If you publish Bad Stuff, we may delete it from the registry, or evenban your account in extreme cases. So don't do that.

When you find issues, please report them:

• web:https://github.com/npm/npm/issues

Be sure to includeall of the output from the npm command that didn't workas expected. Thenpm-debug.log file is also helpful to provide.

You can also look for isaacs in #node.js on irc://irc.freenode.net. Hewill no doubt tell you to put the output in a gist or email.

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