summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/using-npm/config.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/using-npm/config.md')
-rw-r--r--deps/npm/docs/content/using-npm/config.md461
1 files changed, 0 insertions, 461 deletions
diff --git a/deps/npm/docs/content/using-npm/config.md b/deps/npm/docs/content/using-npm/config.md
index cd13237f34..d48f12eb80 100644
--- a/deps/npm/docs/content/using-npm/config.md
+++ b/deps/npm/docs/content/using-npm/config.md
@@ -59,9 +59,6 @@ internal to npm, and are defaults if nothing else is specified.
The following shorthands are parsed on the command-line:
-<!-- AUTOGENERATED CONFIG SHORTHANDS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
* `-a`: `--all`
* `--enjoy-by`: `--before`
* `-c`: `--call`
@@ -103,10 +100,6 @@ The following shorthands are parsed on the command-line:
* `--ws`: `--workspaces`
* `-y`: `--yes`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-<!-- AUTOGENERATED CONFIG SHORTHANDS END -->
-
If the specified configuration param resolves unambiguously to a known
configuration parameter, then it is expanded to that configuration
parameter. For example:
@@ -130,9 +123,6 @@ npm ls --global --parseable --long --loglevel info
### Config Settings
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
#### `_auth`
* Default: null
@@ -146,9 +136,6 @@ Warning: This should generally not be set via a command-line option. It is
safer to use a registry-provided authentication bearer token stored in the
~/.npmrc file by running `npm login`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `access`
* Default: 'restricted' for scoped packages, 'public' for unscoped packages
@@ -165,9 +152,6 @@ subsequent `npm publish` commands using the `--access` flag will not have an
effect to the access level. To make changes to the access level after the
initial publish use `npm access`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `all`
* Default: false
@@ -177,9 +161,6 @@ When running `npm outdated` and `npm ls`, setting `--all` will show all
outdated or installed packages, rather than only those directly depended
upon by the current project.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `allow-same-version`
* Default: false
@@ -188,9 +169,6 @@ upon by the current project.
Prevents throwing an error when `npm version` is used to set the new version
to the same value as the current version.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `audit`
* Default: true
@@ -201,9 +179,6 @@ default registry and all registries configured for scopes. See the
documentation for [`npm audit`](/commands/npm-audit) for details on what is
submitted.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `audit-level`
* Default: null
@@ -212,9 +187,6 @@ submitted.
The minimum level of vulnerability for `npm audit` to exit with a non-zero
exit code.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `auth-type`
* Default: "legacy"
@@ -225,9 +197,6 @@ removed in a future version.
What authentication strategy to use with `login`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `before`
* Default: null
@@ -243,9 +212,6 @@ If the requested version is a `dist-tag` and the given tag does not pass the
will be used. For example, `foo@latest` might install `foo@1.2` even though
`latest` is `2.0`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `bin-links`
* Default: true
@@ -258,9 +224,6 @@ Set to false to have it not do this. This can be used to work around the
fact that some file systems don't support symlinks, even on ostensibly Unix
systems.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `browser`
* Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"`
@@ -273,9 +236,6 @@ terminal.
Set to `true` to use default system URL opener.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `ca`
* Default: null
@@ -302,9 +262,6 @@ ca[]="..."
See also the `strict-ssl` config.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cache`
* Default: Windows: `%LocalAppData%\npm-cache`, Posix: `~/.npm`
@@ -313,9 +270,6 @@ See also the `strict-ssl` config.
The location of npm's cache directory. See [`npm
cache`](/commands/npm-cache)
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cafile`
* Default: null
@@ -325,9 +279,6 @@ A path to a file containing one or multiple Certificate Authority signing
certificates. Similar to the `ca` setting, but allows for multiple CA's, as
well as for the CA information to be stored in a file on disk.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `call`
* Default: ""
@@ -341,9 +292,6 @@ npm exec --package yo --package generator-node --call "yo node"
```
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cert`
* Default: null
@@ -361,9 +309,6 @@ It is _not_ the path to a certificate file, though you can set a
registry-scoped "certfile" path like
"//other-registry.tld/:certfile=/path/to/cert.pem".
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `ci-name`
* Default: The name of the current CI system, or `null` when not on a known CI
@@ -374,9 +319,6 @@ The name of a continuous integration system. If not set explicitly, npm will
detect the current CI environment using the
[`@npmcli/ci-detect`](http://npm.im/@npmcli/ci-detect) module.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cidr`
* Default: null
@@ -385,9 +327,6 @@ detect the current CI environment using the
This is a list of CIDR address to be used when configuring limited access
tokens with the `npm token create` command.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `color`
* Default: true unless the NO_COLOR environ is set to something other than '0'
@@ -396,9 +335,6 @@ tokens with the `npm token create` command.
If false, never shows colors. If `"always"` then always shows colors. If
true, then only prints color codes for tty file descriptors.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `commit-hooks`
* Default: true
@@ -406,9 +342,6 @@ true, then only prints color codes for tty file descriptors.
Run git commit hooks when using the `npm version` command.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `depth`
* Default: `Infinity` if `--all` is set, otherwise `1`
@@ -419,9 +352,6 @@ The depth to go when recursing packages for `npm ls`.
If not set, `npm ls` will show only the immediate dependencies of the root
project. If `--all` is set, then npm will show all dependencies by default.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `description`
* Default: true
@@ -429,9 +359,6 @@ project. If `--all` is set, then npm will show all dependencies by default.
Show the description in `npm search`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff`
* Default:
@@ -439,9 +366,6 @@ Show the description in `npm search`
Define arguments to compare in `npm diff`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-dst-prefix`
* Default: "b/"
@@ -449,9 +373,6 @@ Define arguments to compare in `npm diff`.
Destination prefix to be used in `npm diff` output.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-ignore-all-space`
* Default: false
@@ -459,9 +380,6 @@ Destination prefix to be used in `npm diff` output.
Ignore whitespace when comparing lines in `npm diff`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-name-only`
* Default: false
@@ -469,9 +387,6 @@ Ignore whitespace when comparing lines in `npm diff`.
Prints only filenames when using `npm diff`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-no-prefix`
* Default: false
@@ -482,9 +397,6 @@ Do not show any source or destination prefix in `npm diff` output.
Note: this causes `npm diff` to ignore the `--diff-src-prefix` and
`--diff-dst-prefix` configs.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-src-prefix`
* Default: "a/"
@@ -492,9 +404,6 @@ Note: this causes `npm diff` to ignore the `--diff-src-prefix` and
Source prefix to be used in `npm diff` output.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-text`
* Default: false
@@ -502,9 +411,6 @@ Source prefix to be used in `npm diff` output.
Treat all files as text in `npm diff`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `diff-unified`
* Default: 3
@@ -512,9 +418,6 @@ Treat all files as text in `npm diff`.
The number of lines of context to print in `npm diff`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `dry-run`
* Default: false
@@ -528,9 +431,6 @@ commands that modify your local installation, eg, `install`, `update`,
Note: This is NOT honored by other network related commands, eg `dist-tags`,
`owner`, etc.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `editor`
* Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on
@@ -539,9 +439,6 @@ Note: This is NOT honored by other network related commands, eg `dist-tags`,
The command to run for `npm edit` and `npm config edit`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `engine-strict`
* Default: false
@@ -553,9 +450,6 @@ Node.js version.
This can be overridden by setting the `--force` flag.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fetch-retries`
* Default: 2
@@ -567,9 +461,6 @@ from the registry.
npm will retry idempotent read requests to the registry in the case of
network failures or 5xx HTTP errors.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fetch-retry-factor`
* Default: 10
@@ -577,9 +468,6 @@ network failures or 5xx HTTP errors.
The "factor" config for the `retry` module to use when fetching packages.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fetch-retry-maxtimeout`
* Default: 60000 (1 minute)
@@ -588,9 +476,6 @@ The "factor" config for the `retry` module to use when fetching packages.
The "maxTimeout" config for the `retry` module to use when fetching
packages.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fetch-retry-mintimeout`
* Default: 10000 (10 seconds)
@@ -599,9 +484,6 @@ packages.
The "minTimeout" config for the `retry` module to use when fetching
packages.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fetch-timeout`
* Default: 300000 (5 minutes)
@@ -609,9 +491,6 @@ packages.
The maximum amount of time to wait for HTTP requests to complete.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `force`
* Default: false
@@ -638,9 +517,6 @@ mistakes, unnecessary performance degradation, and malicious input.
If you don't have a clear idea of what you want to do, it is strongly
recommended that you do not use this option!
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `foreground-scripts`
* Default: false
@@ -653,9 +529,6 @@ input, output, and error with the main npm process.
Note that this will generally make installs run slower, and be much noisier,
but can be useful for debugging.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `format-package-lock`
* Default: true
@@ -664,9 +537,6 @@ but can be useful for debugging.
Format `package-lock.json` or `npm-shrinkwrap.json` as a human readable
file.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `fund`
* Default: true
@@ -676,9 +546,6 @@ When "true" displays the message at the end of each `npm install`
acknowledging the number of dependencies looking for funding. See [`npm
fund`](/commands/npm-fund) for details.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `git`
* Default: "git"
@@ -687,9 +554,6 @@ fund`](/commands/npm-fund) for details.
The command to use for git commands. If git is installed on the computer,
but is not in the `PATH`, then set this to the full path to the git binary.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `git-tag-version`
* Default: true
@@ -698,9 +562,6 @@ but is not in the `PATH`, then set this to the full path to the git binary.
Tag the commit when using the `npm version` command. Setting this to false
results in no commit being made at all.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `global`
* Default: false
@@ -715,9 +576,6 @@ folder instead of the current working directory. See
* bin files are linked to `{prefix}/bin`
* man pages are linked to `{prefix}/share/man`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `global-style`
* Default: false
@@ -730,9 +588,6 @@ on will be flattened in their `node_modules` folders. This obviously will
eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling`
will be preferred.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `globalconfig`
* Default: The global --prefix setting plus 'etc/npmrc'. For example,
@@ -741,9 +596,6 @@ will be preferred.
The config file to read for global config options.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `heading`
* Default: "npm"
@@ -751,9 +603,6 @@ The config file to read for global config options.
The string that starts all the debugging log output.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `https-proxy`
* Default: null
@@ -764,9 +613,6 @@ A proxy to use for outgoing https requests. If the `HTTPS_PROXY` or
proxy settings will be honored by the underlying `make-fetch-happen`
library.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `if-present`
* Default: false
@@ -781,9 +627,6 @@ CI setup.
This value is not exported to the environment for child processes.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `ignore-scripts`
* Default: false
@@ -796,9 +639,6 @@ Note that commands explicitly intended to run a particular script, such as
will still run their intended script if `ignore-scripts` is set, but they
will *not* run any pre- or post-scripts.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `include`
* Default:
@@ -811,9 +651,6 @@ This is the inverse of `--omit=<type>`.
Dependency types specified in `--include` will not be omitted, regardless of
the order in which omit/include are specified on the command-line.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `include-staged`
* Default: false
@@ -824,9 +661,6 @@ Allow installing "staged" published packages, as defined by [npm RFC PR
This is experimental, and not implemented by the npm public registry.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `include-workspace-root`
* Default: false
@@ -840,9 +674,6 @@ the specified workspaces, and not on the root project.
This value is not exported to the environment for child processes.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-author-email`
* Default: ""
@@ -850,9 +681,6 @@ This value is not exported to the environment for child processes.
The value `npm init` should use by default for the package author's email.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-author-name`
* Default: ""
@@ -860,9 +688,6 @@ The value `npm init` should use by default for the package author's email.
The value `npm init` should use by default for the package author's name.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-author-url`
* Default: ""
@@ -871,9 +696,6 @@ The value `npm init` should use by default for the package author's name.
The value `npm init` should use by default for the package author's
homepage.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-license`
* Default: "ISC"
@@ -881,9 +703,6 @@ homepage.
The value `npm init` should use by default for the package license.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-module`
* Default: "~/.npm-init.js"
@@ -894,9 +713,6 @@ documentation for the
[init-package-json](https://github.com/npm/init-package-json) module for
more information, or [npm init](/commands/npm-init).
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init-version`
* Default: "1.0.0"
@@ -905,9 +721,6 @@ more information, or [npm init](/commands/npm-init).
The value that `npm init` should use by default for the package version
number, if not already set in package.json.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `install-links`
* Default: false
@@ -917,9 +730,6 @@ When set file: protocol dependencies that exist outside of the project root
will be packed and installed as regular dependencies instead of creating a
symlink. This option has no effect on workspaces.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `json`
* Default: false
@@ -932,9 +742,6 @@ Whether or not to output JSON data, rather than the normal output.
Not supported by all npm commands.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `key`
* Default: null
@@ -950,9 +757,6 @@ key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----"
It is _not_ the path to a key file, though you can set a registry-scoped
"keyfile" path like "//other-registry.tld/:keyfile=/path/to/key.pem".
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `legacy-bundling`
* Default: false
@@ -963,9 +767,6 @@ such as the one included with node 0.8, can install the package. This
eliminates all automatic deduping. If used with `global-style` this option
will be preferred.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `legacy-peer-deps`
* Default: false
@@ -984,9 +785,6 @@ This differs from `--omit=peer`, in that `--omit=peer` will avoid unpacking
Use of `legacy-peer-deps` is not recommended, as it will not enforce the
`peerDependencies` contract that meta-dependencies may rely on.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `link`
* Default: false
@@ -994,9 +792,6 @@ Use of `legacy-peer-deps` is not recommended, as it will not enforce the
Used with `npm ls`, limiting output to only those packages that are linked.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `local-address`
* Default: null
@@ -1005,9 +800,6 @@ Used with `npm ls`, limiting output to only those packages that are linked.
The IP address of the local interface to use when making connections to the
npm registry. Must be IPv4 in versions of Node prior to 0.12.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `location`
* Default: "user" unless `--global` is passed, which will also set this value
@@ -1025,9 +817,6 @@ instead of the current working directory. See
* bin files are linked to `{prefix}/bin`
* man pages are linked to `{prefix}/share/man`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `lockfile-version`
* Default: Version 2 if no lockfile or current lockfile version less than or
@@ -1050,9 +839,6 @@ and interoperability, at the expense of more bytes on disk.
disk than lockfile version 2, but not interoperable with older npm versions.
Ideal if all users are on npm version 7 and higher.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `loglevel`
* Default: "notice"
@@ -1067,9 +853,6 @@ Any logs of a higher level than the setting are shown. The default is
See also the `foreground-scripts` config.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `logs-dir`
* Default: A directory named `_logs` inside the cache
@@ -1078,9 +861,6 @@ See also the `foreground-scripts` config.
The location of npm's log directory. See [`npm logging`](/using-npm/logging)
for more information.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `logs-max`
* Default: 10
@@ -1090,9 +870,6 @@ The maximum number of log files to store.
If set to 0, no log files will be written for the current run.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `long`
* Default: false
@@ -1100,9 +877,6 @@ If set to 0, no log files will be written for the current run.
Show extended information in `ls`, `search`, and `help-search`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `maxsockets`
* Default: 15
@@ -1111,9 +885,6 @@ Show extended information in `ls`, `search`, and `help-search`.
The maximum number of connections to use per origin (protocol/host/port
combination).
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `message`
* Default: "%s"
@@ -1123,9 +894,6 @@ Commit message which is used by `npm version` when creating version commit.
Any "%s" in the message will be replaced with the version number.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `node-options`
* Default: null
@@ -1135,9 +903,6 @@ Options to pass through to Node.js via the `NODE_OPTIONS` environment
variable. This does not impact how npm itself is executed but it does impact
how lifecycle scripts are called.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `node-version`
* Default: Node.js `process.version` value
@@ -1145,9 +910,6 @@ how lifecycle scripts are called.
The node version to use when checking a package's `engines` setting.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `noproxy`
* Default: The value of the NO_PROXY environment variable
@@ -1157,9 +919,6 @@ Domain extensions that should bypass any proxies.
Also accepts a comma-delimited string.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `npm-version`
* Default: Output of `npm --version`
@@ -1167,9 +926,6 @@ Also accepts a comma-delimited string.
The npm version to use when checking a package's `engines` setting.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `offline`
* Default: false
@@ -1178,9 +934,6 @@ The npm version to use when checking a package's `engines` setting.
Force offline mode: no network requests will be done during install. To
allow the CLI to fill in missing cache data, see `--prefer-offline`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `omit`
* Default: 'dev' if the `NODE_ENV` environment variable is set to
@@ -1199,9 +952,6 @@ it will be included.
If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment
variable will be set to `'production'` for all lifecycle scripts.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `omit-lockfile-registry-resolved`
* Default: false
@@ -1212,9 +962,6 @@ registry dependencies. Subsequent installs will need to resolve tarball
endpoints with the configured registry, likely resulting in a longer install
time.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `otp`
* Default: null
@@ -1226,9 +973,6 @@ when publishing or changing package permissions with `npm access`.
If not set, and a registry response fails with a challenge for a one-time
password, npm will prompt on the command line for one.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `pack-destination`
* Default: "."
@@ -1236,9 +980,6 @@ password, npm will prompt on the command line for one.
Directory in which `npm pack` will save tarballs.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `package`
* Default:
@@ -1246,9 +987,6 @@ Directory in which `npm pack` will save tarballs.
The package or packages to install for [`npm exec`](/commands/npm-exec)
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `package-lock`
* Default: true
@@ -1259,9 +997,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true.
This configuration does not affect `npm ci`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `package-lock-only`
* Default: false
@@ -1276,9 +1011,6 @@ instead of checking `node_modules` and downloading dependencies.
For `list` this means the output will be based on the tree described by the
`package-lock.json`, rather than the contents of `node_modules`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `parseable`
* Default: false
@@ -1287,9 +1019,6 @@ For `list` this means the output will be based on the tree described by the
Output parseable results from commands that write to standard output. For
`npm search`, this will be tab-separated table format.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `prefer-offline`
* Default: false
@@ -1299,9 +1028,6 @@ If true, staleness checks for cached data will be bypassed, but missing data
will be requested from the server. To force full offline mode, use
`--offline`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `prefer-online`
* Default: false
@@ -1310,9 +1036,6 @@ will be requested from the server. To force full offline mode, use
If true, staleness checks for cached data will be forced, making the CLI
look for updates immediately even for fresh package data.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `prefix`
* Default: In global mode, the folder where the node executable is installed.
@@ -1323,9 +1046,6 @@ look for updates immediately even for fresh package data.
The location to install global items. If set on the command line, then it
forces non-global commands to run in the specified folder.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `preid`
* Default: ""
@@ -1334,9 +1054,6 @@ forces non-global commands to run in the specified folder.
The "prerelease identifier" to use as a prefix for the "prerelease" part of
a semver. Like the `rc` in `1.2.0-rc.8`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `progress`
* Default: `true` unless running in a known CI system
@@ -1347,9 +1064,6 @@ operations, if `process.stderr` is a TTY.
Set to `false` to suppress the progress bar.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `proxy`
* Default: null
@@ -1359,9 +1073,6 @@ A proxy to use for outgoing http requests. If the `HTTP_PROXY` or
`http_proxy` environment variables are set, proxy settings will be honored
by the underlying `request` library.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `read-only`
* Default: false
@@ -1370,9 +1081,6 @@ by the underlying `request` library.
This is used to mark a token as unable to publish when configuring limited
access tokens with the `npm token create` command.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `rebuild-bundle`
* Default: true
@@ -1380,9 +1088,6 @@ access tokens with the `npm token create` command.
Rebuild bundled dependencies after installation.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `registry`
* Default: "https://registry.npmjs.org/"
@@ -1390,9 +1095,6 @@ Rebuild bundled dependencies after installation.
The base URL of the npm registry.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `replace-registry-host`
* Default: "npmjs"
@@ -1408,9 +1110,6 @@ registry host with the configured host every time.
You may also specify a bare hostname (e.g., "registry.npmjs.org").
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save`
* Default: `true` unless when using `npm update` where it defaults to `false`
@@ -1423,9 +1122,6 @@ When used with the `npm rm` command, removes the dependency from
Will also prevent writing to `package-lock.json` if set to `false`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-bundle`
* Default: false
@@ -1437,9 +1133,6 @@ If a package would be saved at install time by the use of `--save`,
Ignored if `--save-peer` is set, since peerDependencies cannot be bundled.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-dev`
* Default: false
@@ -1447,9 +1140,6 @@ Ignored if `--save-peer` is set, since peerDependencies cannot be bundled.
Save installed packages to a package.json file as `devDependencies`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-exact`
* Default: false
@@ -1458,9 +1148,6 @@ Save installed packages to a package.json file as `devDependencies`.
Dependencies saved to package.json will be configured with an exact version
rather than using npm's default semver range operator.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-optional`
* Default: false
@@ -1468,9 +1155,6 @@ rather than using npm's default semver range operator.
Save installed packages to a package.json file as `optionalDependencies`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-peer`
* Default: false
@@ -1478,9 +1162,6 @@ Save installed packages to a package.json file as `optionalDependencies`.
Save installed packages to a package.json file as `peerDependencies`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-prefix`
* Default: "^"
@@ -1494,9 +1175,6 @@ to `^1.2.3` which allows minor upgrades for that package, but after `npm
config set save-prefix='~'` it would be set to `~1.2.3` which only allows
patch upgrades.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `save-prod`
* Default: false
@@ -1509,9 +1187,6 @@ you want to move it to be a non-optional production dependency.
This is the default behavior if `--save` is true, and neither `--save-dev`
or `--save-optional` are true.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `scope`
* Default: the scope of the current project, if any, or ""
@@ -1542,9 +1217,6 @@ npm init --scope=@foo --yes
```
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `script-shell`
* Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows
@@ -1553,9 +1225,6 @@ npm init --scope=@foo --yes
The shell to use for scripts run with the `npm exec`, `npm run` and `npm
init <package-spec>` commands.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `searchexclude`
* Default: ""
@@ -1563,9 +1232,6 @@ init <package-spec>` commands.
Space-separated options that limit the results from search.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `searchlimit`
* Default: 20
@@ -1574,9 +1240,6 @@ Space-separated options that limit the results from search.
Number of items to limit search results to. Will not apply at all to legacy
searches.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `searchopts`
* Default: ""
@@ -1584,9 +1247,6 @@ searches.
Space-separated options that are always passed to search.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `searchstaleness`
* Default: 900
@@ -1595,9 +1255,6 @@ Space-separated options that are always passed to search.
The age of the cache, in seconds, before another registry request is made if
using legacy search endpoint.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `shell`
* Default: SHELL environment variable, or "bash" on Posix, or "cmd.exe" on
@@ -1606,9 +1263,6 @@ using legacy search endpoint.
The shell to run for the `npm explore` command.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `sign-git-commit`
* Default: false
@@ -1620,9 +1274,6 @@ version using `-S` to add a signature.
Note that git requires you to have set up GPG keys in your git configs for
this to work properly.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `sign-git-tag`
* Default: false
@@ -1634,9 +1285,6 @@ If set to true, then the `npm version` command will tag the version using
Note that git requires you to have set up GPG keys in your git configs for
this to work properly.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `strict-peer-deps`
* Default: false
@@ -1656,9 +1304,6 @@ When such and override is performed, a warning is printed, explaining the
conflict and the packages involved. If `--strict-peer-deps` is set, then
this warning is treated as a failure.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `strict-ssl`
* Default: true
@@ -1669,9 +1314,6 @@ via https.
See also the `ca` config.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `tag`
* Default: "latest"
@@ -1686,9 +1328,6 @@ command, if no explicit tag is given.
When used by the `npm diff` command, this is the tag used to fetch the
tarball that will be compared with the local files by default.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `tag-version-prefix`
* Default: "v"
@@ -1702,9 +1341,6 @@ Because other tools may rely on the convention that npm version tags look
like `v1.0.0`, _only use this property if it is absolutely necessary_. In
particular, use care when overriding this setting for public packages.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `timing`
* Default: false
@@ -1717,9 +1353,6 @@ If true, writes a debug log to `logs-dir` and timing information to
You can quickly view it with this [json](https://npm.im/json) command line:
`npm exec -- json -g < ~/.npm/_timing.json`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `umask`
* Default: 0
@@ -1740,9 +1373,6 @@ Thus, the effective default umask value on most POSIX systems is 0o22,
meaning that folders and executables are created with a mode of 0o755 and
other files are created with a mode of 0o644.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `unicode`
* Default: false on windows, true on mac/unix systems with a unicode locale,
@@ -1752,9 +1382,6 @@ other files are created with a mode of 0o644.
When set to true, npm uses unicode characters in the tree output. When
false, it uses ascii characters instead of unicode glyphs.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `update-notifier`
* Default: true
@@ -1763,9 +1390,6 @@ false, it uses ascii characters instead of unicode glyphs.
Set to false to suppress the update notification when using an older version
of npm than the latest.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `usage`
* Default: false
@@ -1773,9 +1397,6 @@ of npm than the latest.
Show short usage output about the command specified.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `user-agent`
* Default: "npm/{npm-version} node/{node-version} {platform} {arch}
@@ -1794,9 +1415,6 @@ their actual counterparts:
* `{ci}` - The value of the `ci-name` config, if set, prefixed with `ci/`, or
an empty string if `ci-name` is empty.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `userconfig`
* Default: "~/.npmrc"
@@ -1808,9 +1426,6 @@ This may be overridden by the `npm_config_userconfig` environment variable
or the `--userconfig` command line option, but may _not_ be overridden by
settings in the `globalconfig` file.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `version`
* Default: false
@@ -1820,9 +1435,6 @@ If true, output the npm version and exit successfully.
Only relevant when specified explicitly on the command line.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `versions`
* Default: false
@@ -1834,9 +1446,6 @@ exists, and exit successfully.
Only relevant when specified explicitly on the command line.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `viewer`
* Default: "man" on Posix, "browser" on Windows
@@ -1846,9 +1455,6 @@ The program to use to view help content.
Set to `"browser"` to view html help content in the default web browser.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `which`
* Default: null
@@ -1856,9 +1462,6 @@ Set to `"browser"` to view html help content in the default web browser.
If there are multiple funding sources, which 1-indexed source URL to open.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `workspace`
* Default:
@@ -1881,9 +1484,6 @@ brand new workspace within the project.
This value is not exported to the environment for child processes.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `workspaces`
* Default: null
@@ -1902,9 +1502,6 @@ _unless_ one or more workspaces are specified in the `workspace` config.
This value is not exported to the environment for child processes.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `workspaces-update`
* Default: true
@@ -1913,9 +1510,6 @@ This value is not exported to the environment for child processes.
If set to true, the npm cli will run an update after operations that may
possibly change the workspaces installed to the `node_modules` folder.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `yes`
* Default: null
@@ -1924,9 +1518,6 @@ possibly change the workspaces installed to the `node_modules` folder.
Automatically answer "yes" to any prompts that npm might print on the
command line.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `also`
* Default: null
@@ -1935,9 +1526,6 @@ command line.
When set to `dev` or `development`, this is an alias for `--include=dev`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cache-max`
* Default: Infinity
@@ -1946,9 +1534,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`.
`--cache-max=0` is an alias for `--prefer-online`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `cache-min`
* Default: 0
@@ -1957,9 +1542,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`.
`--cache-min=9999 (or bigger)` is an alias for `--prefer-offline`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `dev`
* Default: false
@@ -1968,9 +1550,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`.
Alias for `--include=dev`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.author.email`
* Default: ""
@@ -1979,9 +1558,6 @@ Alias for `--include=dev`.
Alias for `--init-author-email`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.author.name`
* Default: ""
@@ -1990,9 +1566,6 @@ Alias for `--init-author-email`
Alias for `--init-author-name`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.author.url`
* Default: ""
@@ -2001,9 +1574,6 @@ Alias for `--init-author-name`
Alias for `--init-author-url`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.license`
* Default: "ISC"
@@ -2012,9 +1582,6 @@ Alias for `--init-author-url`
Alias for `--init-license`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.module`
* Default: "~/.npm-init.js"
@@ -2023,9 +1590,6 @@ Alias for `--init-license`
Alias for `--init-module`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `init.version`
* Default: "1.0.0"
@@ -2034,9 +1598,6 @@ Alias for `--init-module`
Alias for `--init-version`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `only`
* Default: null
@@ -2045,9 +1606,6 @@ Alias for `--init-version`
When set to `prod` or `production`, this is an alias for `--omit=dev`.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `optional`
* Default: null
@@ -2059,9 +1617,6 @@ Default value does install optional deps unless otherwise omitted.
Alias for --include=optional or --omit=optional
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `production`
* Default: null
@@ -2070,9 +1625,6 @@ Alias for --include=optional or --omit=optional
Alias for `--omit=dev`
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `shrinkwrap`
* Default: true
@@ -2081,9 +1633,6 @@ Alias for `--omit=dev`
Alias for --package-lock
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `sso-poll-frequency`
* Default: 500
@@ -2094,9 +1643,6 @@ Alias for --package-lock
When used with SSO-enabled `auth-type`s, configures how regularly the
registry should be polled while the user is completing authentication.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `sso-type`
* Default: "oauth"
@@ -2106,9 +1652,6 @@ registry should be polled while the user is completing authentication.
If `--auth-type=sso`, the type of SSO type to use.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
#### `tmp`
* Default: The value returned by the Node.js `os.tmpdir()` method
@@ -2121,10 +1664,6 @@ If `--auth-type=sso`, the type of SSO type to use.
Historically, the location where temporary files were stored. No longer
relevant.
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
### See also
* [npm config](/commands/npm-config)