See npm-config for a more thorough discussion of the mechanisms involved. See npmrc for more information about the npmrc files. Npm gets its config settings from the command line, environment variables, npmrc files, and in some cases, the package.json file. NPM Registry Configuration for Command-Line and Build Tools If you are using command-line tools to build your Node.js applications for XS advanced, you can configure the tools to use a particular NPM registry to resolve the dependencies between resources specified in the deployment descriptors. npm config list Opens the config file in an editor. npm config delete Lists all the config settings,could be used to check for existing config entries. npm config get Deletes the key from all configuration files. npm config set Gets the value of an existing configuration key. You can also change configs with the help of - argument. To change registry, you can use command: npm config set registry. You can try to specify registry in a npmrc file, and module in the command line. Npm gets its config settings from the command line, environment variables, and npmrc files. If value is omitted, then it sets it to “true”. Config supports the following sub-commands: set. The npm configcommand can be used to update and edit the contentsof the user and global npmrc files. npm config set registry you can find more information with npm help config command, also check for privileges when and if you are running. The correct command for changing registry is. npmrc file which is the configuration for npm. You shouldn't change the npm registry using.

Npm config set registry