When "true" submit audit reports alongside npm install runs to the default Npm outdated, or npm update, is an alias for -dev. When "dev" or "development" and running local npm shrinkwrap, always-authįorce npm to always require authentication when accessing the registry,
To the same value as the current version. Prevents throwing an error when npm version is used to set the new version Unscoped packages always have an access level of public. The only valid values for access are public and You want your scoped package to be publicly viewable (and installable) set When publishing scoped packages, the access level defaults to restricted. Then the user could change the behavior by doing: npm config set foo:port 80 , "scripts" : Īnd the server.js is this: http.createServer(.).listen(_package_config_port) Keys are overwritten in the environment if there is a config param For example, if the package.json has When running scripts (see npm-scripts) the package.json "config" Npm ls -global -parseable -long -loglevel info Param, then it is expanded to its various component pieces. Resulting combination is unambiguously not some other configuration If multiple single-character shorthands are strung together, and the If the specified configuration param resolves unambiguously to a knownĬonfiguration parameter, then it is expanded to that configuration The following shorthands are parsed on the command-line: Internal to npm, and are defaults if nothing else is specified. Run npm config ls -l to see a set of configuration parameters that are
Option -userconfig or environment variable $NPM_CONFIG_USERCONFIG)
A - argument tells the cli parser to stop Putting -foo bar on the command line sets the foo configuration Npm gets its configuration values from the following sources, sorted by priority: Command Line Flags Npm-config More than you probably want to know about npm configuration Description