


If the HTTPS_PROXY or https_proxy or HTTP_PROXY or http_proxy environment variables are set, proxy settings will be honored by the underlying request library. The string that starts all the debugging log output.Ī proxy to use for outgoing https requests. The group to use when running package scripts in global mode as the root user. If used with legacy-bundling, legacy-bundling will be preferred. This obviously will elminate some deduping. Only your direct dependencies will show in node_modules and everything they depend on will be flattened in their node_modules folders.

The config file to read for global config options.Ĭauses npm to install the package into your local node_modules folder with the same layout it uses with the global node_modules folder. When running scripts (see npm help 7 npm-scripts) the package.json "config" keys are overwritten in the environment if there is a config param of For example, if the package.json has this: Npm ls -global -parseable -long -loglevel info If multiple single-character shorthands are strung together, and the resulting combination is unambiguously not some other configuration param, then it is expanded to its various component pieces. If the specified configuration param resolves unambiguously to a known configuration parameter, then it is expanded to that configuration parameter. 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".
