When running scripts (see npm-scripts) the package.json "config" keys are overwritten in the environment if there is a config param of ]. 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. (see So you might want to try this command : > npm config set cache C:\Devel odejs pm-cache -global Then, run npm -global cache verify after running this command.
Npm builtin config file (/path/to/npm/npmrc) You can change npm cache folder using the npm command line. 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: More than you probably want to know about npm configuration
0 kommentar(er)
