Is determined by looking in the npmPath folder. Of the node executable, or the prefix setting in the cli, env, The globalPrefix folder, which is inferred by looking at the location The userconfig config value can be overridden by the cli, env, or LocalPrefix folder (ie, the cwd, or its nearest parent that containsĮither a node_modules folder or package.json file.) There is no way at this time to modify this prefix. eg npm_config_some_key=some_value in theĮnvironment. It's the one that npm has used forever, and changing it will be

Parsed by nopt, which is not a great choice, but eg -some-key=some-value on the command line. A builtin config, read from a npmrc file in the root of the npm.Userconfig file (defaulting to $PREFIX/etc/npmrc) is used to load The globalconfig value, as set by the environment, CLI, and.The userconfig value, as set by the environment and CLI (defaulting to.Up the folder tree to the first parent containing a node_modulesįolder, package.json file, or package-lock.json file.) Only be set by the CLI config options, and otherwise defaults to a walk The project config file is loaded based on the local prefix (which can.Prefix if specified on the CLI options and not in global mode, or the The prefix config value has some special semantics, setting the local.Those parts make more sense to live within the npm CLI itself. Importantly, does not define all the configuration defaults or types, as It does the management of configuration files that npm uses, but Npmconf, and the code that once lived in npm's

This module is the spiritual descendant of

The code for this module is now maintained inside a workspace of the npm cli itself:

Npm config help