* -v: -version * -h, -?, -help, -H: -usage * -s, -silent: -loglevel silent * -q, -quiet: -loglevel warn * -d: -loglevel info * -dd, -verbose: -loglevel verbose * -ddd: -loglevel silly * -g: -global * -C: -prefix * -l: -long * -m: -message * -p, -porcelain: -parseable * -reg: -registry * -f: -force * -desc: -description * -S: -save * -D: -save-dev * -O: -save-optional * -B: -save-bundle * -E: -save-exact * -y: -yes * -n: -yes false * ll and la commands: ls -long The following shorthands are parsed on the command-line: Run npm config ls -l to see a set of configuration parameters that are internal to npm, and are defaults if nothing else is specified. Npm builtin config file (/path/to/npm/npmrc) Per-project config file (/path/to/my/project/.npmrc) Config values are case-insensitive, so NPM_CONFIG_FOO=bar will work the same. Any environment configurations that are not given a value will be given the value of true. For example, putting npm_config_foo=bar in your environment will set the foo configuration parameter to bar. A -flag parameter that is at the end of the command will be given the value of true.Īny environment variables that start with npm_config_ will be interpreted as a configuration parameter. A - argument tells the cli parser to stop reading flags. Putting -foo bar on the command line sets the foo configuration parameter to "bar". Npm gets its configuration values from the following sources, sorted by priority: NAME npm-config - More than you probably want to know about npm configuration (The comments found at the beginning of the groff file "man7/npm-config.7".) Npm-config (7) Leading comments generated with Ronn/v0.7.3