File Explorer

1.TH "NPM-CONFIG" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-config\fR - Manage the npm configuration files4.SS "Synopsis"5.P6.RS 27.nf8npm config set <key>=<value> \[lB]<key>=<value> ...\[rB]9npm config get \[lB]<key> \[lB]<key> ...\[rB]\[rB]10npm config delete <key> \[lB]<key> ...\[rB]11npm config list \[lB]--json\[rB]12npm config edit13npm config fix14 15alias: c16.fi17.RE18.P19Note: This command is unaware of workspaces.20.SS "Description"21.P22npm gets its config settings from the command line, environment variables, \fBnpmrc\fR files, and in some cases, the \fBpackage.json\fR file.23.P24See npm help npmrc for more information about the npmrc files.25.P26See npm help config for a more thorough explanation of the mechanisms involved, and a full list of config options available.27.P28The \fBnpm config\fR command can be used to update and edit the contents of the user and global npmrc files.29.SS "Sub-commands"30.P31Config supports the following sub-commands:32.SS "set"33.P34.RS 235.nf36npm config set key=value \[lB]key=value...\[rB]37npm set key=value \[lB]key=value...\[rB]38.fi39.RE40.P41Sets each of the config keys to the value provided. Modifies the user configuration file unless \fB\[rs]fBlocation\[rs]fR\fR \fI\(la/commands/npm-config#location\(ra\fR is passed.42.P43If value is omitted, the key will be removed from your config file entirely.44.P45Note: for backwards compatibility, \fBnpm config set key value\fR is supported as an alias for \fBnpm config set key=value\fR.46.SS "get"47.P48.RS 249.nf50npm config get \[lB]key ...\[rB]51npm get \[lB]key ...\[rB]52.fi53.RE54.P55Echo the config value(s) to stdout.56.P57If multiple keys are provided, then the values will be prefixed with the key names.58.P59If no keys are provided, then this command behaves the same as \fBnpm config list\fR.60.SS "list"61.P62.RS 263.nf64npm config list65.fi66.RE67.P68Show all the config settings. Use \fB-l\fR to also show defaults. Use \fB--json\fR to show the settings in json format.69.SS "delete"70.P71.RS 272.nf73npm config delete key \[lB]key ...\[rB]74.fi75.RE76.P77Deletes the specified keys from all configuration files.78.SS "edit"79.P80.RS 281.nf82npm config edit83.fi84.RE85.P86Opens the config file in an editor. Use the \fB--global\fR flag to edit the global config.87.SS "fix"88.P89.RS 290.nf91npm config fix92.fi93.RE94.P95Attempts to repair invalid configuration items. Usually this means attaching authentication config (i.e. \fB_auth\fR, \fB_authToken\fR) to the configured \fBregistry\fR.96.SS "Configuration"97.SS "\fBjson\fR"98.RS 099.IP \(bu 4100Default: false101.IP \(bu 4102Type: Boolean103.RE 0104 105.P106Whether or not to output JSON data, rather than the normal output.107.RS 0108.IP \(bu 4109In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.110.RE 0111 112.P113Not supported by all npm commands.114.SS "\fBglobal\fR"115.RS 0116.IP \(bu 4117Default: false118.IP \(bu 4119Type: Boolean120.RE 0121 122.P123Operates in "global" mode, so that packages are installed into the \fBprefix\fR folder instead of the current working directory. See npm help folders for more on the differences in behavior.124.RS 0125.IP \(bu 4126packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.127.IP \(bu 4128bin files are linked to \fB{prefix}/bin\fR129.IP \(bu 4130man pages are linked to \fB{prefix}/share/man\fR131.RE 0132 133.SS "\fBeditor\fR"134.RS 0135.IP \(bu 4136Default: The EDITOR or VISUAL environment variables, or '%SYSTEMROOT%\[rs]notepad.exe' on Windows, or 'vi' on Unix systems137.IP \(bu 4138Type: String139.RE 0140 141.P142The command to run for \fBnpm edit\fR and \fBnpm config edit\fR.143.SS "\fBlocation\fR"144.RS 0145.IP \(bu 4146Default: "user" unless \fB--global\fR is passed, which will also set this value to "global"147.IP \(bu 4148Type: "global", "user", or "project"149.RE 0150 151.P152When passed to \fBnpm config\fR this refers to which config file to use.153.P154When set to "global" mode, packages are installed into the \fBprefix\fR folder instead of the current working directory. See npm help folders for more on the differences in behavior.155.RS 0156.IP \(bu 4157packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.158.IP \(bu 4159bin files are linked to \fB{prefix}/bin\fR160.IP \(bu 4161man pages are linked to \fB{prefix}/share/man\fR162.RE 0163 164.SS "\fBlong\fR"165.RS 0166.IP \(bu 4167Default: false168.IP \(bu 4169Type: Boolean170.RE 0171 172.P173Show extended information in \fBls\fR, \fBsearch\fR, and \fBhelp-search\fR.174.SS "See Also"175.RS 0176.IP \(bu 4177npm help folders178.IP \(bu 4179npm help config180.IP \(bu 4181\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR182.IP \(bu 4183npm help npmrc184.IP \(bu 4185npm help npm186.RE 0187