npm-config
manages npm configuration
TLDR
List all config
$ npm config list
Get config valuecopy
$ npm config get [registry]
Set config valuecopy
$ npm config set [registry] [https://registry.npmjs.org/]
Delete configcopy
$ npm config delete [key]
Edit config filecopy
$ npm config edit
List all with defaultscopy
$ npm config list -l
Set global configcopy
$ npm config set [key] [value] -g
copy
SYNOPSIS
npm config [command] [options]
DESCRIPTION
npm config manages npm configuration across multiple levels. It reads settings from the command line, environment variables, and .npmrc files (project, user, and global).Configuration files are plain ini-formatted lists of key = value pairs. Environment variables prefixed with npm_config_ are also recognized as configuration settings.
PARAMETERS
set KEY=VALUE
Set a config value.get KEY
Echo a config value to stdout.list
Show all config settings. Use -l to show defaults. Use --json for JSON output.delete KEY
Remove a key from all configuration files.edit
Open the config file in an editor. Use --global to edit the global config.fix
Repair invalid configuration entries.-g, --global
Operate on the global configuration file.--location user|global|project
Target a specific configuration level.
CAVEATS
Multiple .npmrc locations exist with a precedence order: project > user > global > defaults. Credentials and tokens may be stored in .npmrc files.
HISTORY
npm config is the configuration management system for npm behavior customization.