npm installs packages into the install prefix at prefix/lib/node_modules and bins are installed in prefix/bin.
npm installs packages into the current project directory, which defaults to the current working directory. Packages are installed to ./node_modules, and bins are installed to ./node_modules/.bin.
Local mode is the default. Use --global or -g on any command to operate in global mode instead.
If youre using npm to develop and publish your code, check out the following help topics:
o json: Make a package.json file. See npm help 5 package.json. o link: For linking your current working code into Nodes path, so that you dont have to reinstall every time you make a change. Use npm link to do this. o install: Its a good idea to install things if you dont need the symbolic link. Especially, installing other peoples code from the registry is done via npm install o adduser: Create an account or log in. Credentials are stored in the user config file. o publish: Use the npm publish command to upload your code to the registry.
npm is extremely configurable. It reads its configuration options from 5 places.
o Command line switches:
Set a config with --key val. All keys take a value, even if they are booleans (the config parser doesnt know what the options are at the time of parsing.) If no value is provided, then the option is set to boolean true.
o Environment Variables:
Set any config by prefixing the name in an environment variable with npm_config_. For example, export npm_config_key=val.
o User Configs:
The file at $HOME/.npmrc is an ini-formatted list of configs. If present, it is parsed. If the userconfig option is set in the cli or env, then that will be used instead.
o Global Configs:
The file found at ../etc/npmrc (from the node executable, by default this resolves to /usr/local/etc/npmrc) will be parsed if it is found. If the globalconfig option is set in the cli, env, or user config, then that file is parsed instead.
npms default configuration options are defined in lib/utils/config-defs.js. These must not be changed.
See npm help 7 npm-config for much much more information.
o code: Read through npm help 7 npm-coding-style if you plan to submit code. You dont have to agree with it, but you do have to follow it. o docs: If you find an error in the documentation, edit the appropriate markdown file in the "doc" folder. (Dont worry about generating the man page.)
Contributors are listed in npms package.json file. You can view them easily by doing npm view npm contributors.
If you would like to contribute, but dont know what to work on, check the issues list or ask on the mailing list.
o http://github.com/npm/npm/issues o firstname.lastname@example.org
When you find issues, please report them:
o web: http://github.com/npm/npm/issues o email: email@example.com
Be sure to include all of the output from the npm command that didnt work as expected. The npm-debug.log file is also helpful to provide.
You can also look for isaacs in #node.js on irc://irc.freenode.net. He will no doubt tell you to put the output in a gist or email.
o npm help help o npm help 7 faq o README o npm help 5 package.json o npm help install o npm help config o npm help 7 config o npm help 5 npmrc o npm help 7 index o npm apihelp npm
|NPM (1)||October 2015|