deps: upgrade npm to 11.6.1

PR-URL: https://github.com/nodejs/node/pull/60012
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
This commit is contained in:
npm CLI robot 2025-10-02 15:30:58 -07:00 committed by GitHub
parent 0eda17ba20
commit 5d843c914e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1030 changed files with 39215 additions and 43367 deletions

View File

@ -27,7 +27,7 @@ packages will *also* show the paths to the specified packages. For
example, running `npm ls promzard` in npm's source tree will show:
```bash
npm@11.6.0 /path/to/npm
npm@11.6.1 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
```

View File

@ -14,7 +14,7 @@ Note: This command is unaware of workspaces.
### Version
11.6.0
11.6.1
### Description

View File

@ -96,9 +96,9 @@ to override default configs in a standard and consistent manner.
### Auth related configuration
The settings `_auth`, `_authToken`, `username` and `_password` must all be
scoped to a specific registry. This ensures that `npm` will never send
credentials to the wrong host.
The settings `_auth`, `_authToken`, `username`, `_password`, `certfile`,
and `keyfile` must all be scoped to a specific registry. This ensures that
`npm` will never send credentials to the wrong host.
The full list is:
- `_auth` (base64 authentication string)
@ -107,6 +107,7 @@ The full list is:
- `_password`
- `email`
- `cafile` (path to certificate authority file)
- `certfile` (path to certificate file)
- `keyfile` (path to key file)
In order to scope these values, they must be prefixed by a URI fragment.

View File

@ -1866,9 +1866,9 @@ When set to `dev` or `development`, this is an alias for `--include=dev`.
* Default: null
* Type: null or String
* DEPRECATED: `key` and `cert` are no longer used for most registry
operations. Use registry scoped `keyfile` and `cafile` instead. Example:
operations. Use registry scoped `keyfile` and `certfile` instead. Example:
//other-registry.tld/:keyfile=/path/to/key.pem
//other-registry.tld/:cafile=/path/to/cert.crt
//other-registry.tld/:certfile=/path/to/cert.crt
A client certificate to pass when accessing the registry. Values should be
in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with
@ -1879,8 +1879,8 @@ cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
```
It is _not_ the path to a certificate file, though you can set a
registry-scoped "cafile" path like
"//other-registry.tld/:cafile=/path/to/cert.pem".
registry-scoped "certfile" path like
"//other-registry.tld/:certfile=/path/to/cert.pem".
@ -1971,9 +1971,9 @@ Alias for `--init-version`
* Default: null
* Type: null or String
* DEPRECATED: `key` and `cert` are no longer used for most registry
operations. Use registry scoped `keyfile` and `cafile` instead. Example:
operations. Use registry scoped `keyfile` and `certfile` instead. Example:
//other-registry.tld/:keyfile=/path/to/key.pem
//other-registry.tld/:cafile=/path/to/cert.crt
//other-registry.tld/:certfile=/path/to/cert.crt
A client key to pass when accessing the registry. Values should be in PEM
format with newlines replaced by the string "\n". For example:

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-access----1160">
<h1 id="----npm-access----1161">
<span>npm-access</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Set access level on published packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-adduser----1160">
<h1 id="----npm-adduser----1161">
<span>npm-adduser</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Add a registry user account</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-audit----1160">
<h1 id="----npm-audit----1161">
<span>npm-audit</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Run a security audit</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-bugs----1160">
<h1 id="----npm-bugs----1161">
<span>npm-bugs</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Report bugs for a package in a web browser</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-cache----1160">
<h1 id="----npm-cache----1161">
<span>npm-cache</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manipulates packages cache</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-ci----1160">
<h1 id="----npm-ci----1161">
<span>npm-ci</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Clean install a project</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-completion----1160">
<h1 id="----npm-completion----1161">
<span>npm-completion</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Tab Completion for npm</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-config----1160">
<h1 id="----npm-config----1161">
<span>npm-config</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manage the npm configuration files</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-dedupe----1160">
<h1 id="----npm-dedupe----1161">
<span>npm-dedupe</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Reduce duplication in the package tree</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-deprecate----1160">
<h1 id="----npm-deprecate----1161">
<span>npm-deprecate</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Deprecate a version of a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-diff----1160">
<h1 id="----npm-diff----1161">
<span>npm-diff</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">The registry diff command</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-dist-tag----1160">
<h1 id="----npm-dist-tag----1161">
<span>npm-dist-tag</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Modify package distribution tags</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-docs----1160">
<h1 id="----npm-docs----1161">
<span>npm-docs</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Open documentation for a package in a web browser</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-doctor----1160">
<h1 id="----npm-doctor----1161">
<span>npm-doctor</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Check the health of your npm environment</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-edit----1160">
<h1 id="----npm-edit----1161">
<span>npm-edit</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Edit an installed package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-exec----1160">
<h1 id="----npm-exec----1161">
<span>npm-exec</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Run a command from a local or remote npm package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-explain----1160">
<h1 id="----npm-explain----1161">
<span>npm-explain</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Explain installed packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-explore----1160">
<h1 id="----npm-explore----1161">
<span>npm-explore</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Browse an installed package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-find-dupes----1160">
<h1 id="----npm-find-dupes----1161">
<span>npm-find-dupes</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Find duplication in the package tree</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-fund----1160">
<h1 id="----npm-fund----1161">
<span>npm-fund</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Retrieve funding information</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-help-search----1160">
<h1 id="----npm-help-search----1161">
<span>npm-help-search</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Search npm help documentation</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-help----1160">
<h1 id="----npm-help----1161">
<span>npm-help</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Get help on npm</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-init----1160">
<h1 id="----npm-init----1161">
<span>npm-init</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Create a package.json file</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-install-ci-test----1160">
<h1 id="----npm-install-ci-test----1161">
<span>npm-install-ci-test</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Install a project with a clean slate and run tests</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-install-test----1160">
<h1 id="----npm-install-test----1161">
<span>npm-install-test</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Install package(s) and run tests</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-install----1160">
<h1 id="----npm-install----1161">
<span>npm-install</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Install a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-link----1160">
<h1 id="----npm-link----1161">
<span>npm-link</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Symlink a package folder</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-login----1160">
<h1 id="----npm-login----1161">
<span>npm-login</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Login to a registry user account</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-logout----1160">
<h1 id="----npm-logout----1161">
<span>npm-logout</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Log out of the registry</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-ls----1160">
<h1 id="----npm-ls----1161">
<span>npm-ls</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">List installed packages</span>
</header>
@ -168,7 +168,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code>
the results to only the paths to the packages named. Note that nested
packages will <em>also</em> show the paths to the specified packages. For
example, running <code>npm ls promzard</code> in npm's source tree will show:</p>
<pre><code class="language-bash">npm@11.6.0 /path/to/npm
<pre><code class="language-bash">npm@11.6.1 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
</code></pre>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-org----1160">
<h1 id="----npm-org----1161">
<span>npm-org</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manage orgs</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-outdated----1160">
<h1 id="----npm-outdated----1161">
<span>npm-outdated</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Check for outdated packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-owner----1160">
<h1 id="----npm-owner----1161">
<span>npm-owner</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manage package owners</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-pack----1160">
<h1 id="----npm-pack----1161">
<span>npm-pack</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Create a tarball from a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-ping----1160">
<h1 id="----npm-ping----1161">
<span>npm-ping</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Ping npm registry</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-pkg----1160">
<h1 id="----npm-pkg----1161">
<span>npm-pkg</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manages your package.json</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-prefix----1160">
<h1 id="----npm-prefix----1161">
<span>npm-prefix</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Display prefix</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-profile----1160">
<h1 id="----npm-profile----1161">
<span>npm-profile</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Change settings on your registry profile</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-prune----1160">
<h1 id="----npm-prune----1161">
<span>npm-prune</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Remove extraneous packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-publish----1160">
<h1 id="----npm-publish----1161">
<span>npm-publish</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Publish a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-query----1160">
<h1 id="----npm-query----1161">
<span>npm-query</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Dependency selector query</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-rebuild----1160">
<h1 id="----npm-rebuild----1161">
<span>npm-rebuild</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Rebuild a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-repo----1160">
<h1 id="----npm-repo----1161">
<span>npm-repo</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Open package repository page in the browser</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-restart----1160">
<h1 id="----npm-restart----1161">
<span>npm-restart</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Restart a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-root----1160">
<h1 id="----npm-root----1161">
<span>npm-root</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Display npm root</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-run----1160">
<h1 id="----npm-run----1161">
<span>npm-run</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Run arbitrary package scripts</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-sbom----1160">
<h1 id="----npm-sbom----1161">
<span>npm-sbom</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Generate a Software Bill of Materials (SBOM)</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-search----1160">
<h1 id="----npm-search----1161">
<span>npm-search</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Search for packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-shrinkwrap----1160">
<h1 id="----npm-shrinkwrap----1161">
<span>npm-shrinkwrap</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Lock down dependency versions for publication</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-star----1160">
<h1 id="----npm-star----1161">
<span>npm-star</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Mark your favorite packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-stars----1160">
<h1 id="----npm-stars----1161">
<span>npm-stars</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">View packages marked as favorites</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-start----1160">
<h1 id="----npm-start----1161">
<span>npm-start</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Start a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-stop----1160">
<h1 id="----npm-stop----1161">
<span>npm-stop</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Stop a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-team----1160">
<h1 id="----npm-team----1161">
<span>npm-team</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manage organization teams and team memberships</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-test----1160">
<h1 id="----npm-test----1161">
<span>npm-test</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Test a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-token----1160">
<h1 id="----npm-token----1161">
<span>npm-token</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Manage your authentication tokens</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-undeprecate----1160">
<h1 id="----npm-undeprecate----1161">
<span>npm-undeprecate</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Undeprecate a version of a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-uninstall----1160">
<h1 id="----npm-uninstall----1161">
<span>npm-uninstall</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Remove a package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-unpublish----1160">
<h1 id="----npm-unpublish----1161">
<span>npm-unpublish</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Remove a package from the registry</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-unstar----1160">
<h1 id="----npm-unstar----1161">
<span>npm-unstar</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Remove an item from your favorite packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-update----1160">
<h1 id="----npm-update----1161">
<span>npm-update</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Update packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-version----1160">
<h1 id="----npm-version----1161">
<span>npm-version</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Bump a package version</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-view----1160">
<h1 id="----npm-view----1161">
<span>npm-view</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">View registry info</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-whoami----1160">
<h1 id="----npm-whoami----1161">
<span>npm-whoami</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Display npm username</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm----1160">
<h1 id="----npm----1161">
<span>npm</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">javascript package manager</span>
</header>
@ -158,7 +158,7 @@ npm command-line interface
</code></pre>
<p>Note: This command is unaware of workspaces.</p>
<h3 id="version">Version</h3>
<p>11.6.0</p>
<p>11.6.1</p>
<h3 id="description">Description</h3>
<p>npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npx----1160">
<h1 id="----npx----1161">
<span>npx</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Run a command from a local or remote npm package</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----folders----1160">
<h1 id="----folders----1161">
<span>folders</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Folder Structures Used by npm</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----install----1160">
<h1 id="----install----1161">
<span>install</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Download and install node and npm</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----folders----1160">
<h1 id="----folders----1161">
<span>folders</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Folder Structures Used by npm</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----packagejson----1160">
<h1 id="----packagejson----1161">
<span>package.json</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Specifics of npm's package.json handling</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npm-shrinkwrapjson----1160">
<h1 id="----npm-shrinkwrapjson----1161">
<span>npm-shrinkwrap.json</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">A publishable lockfile</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----npmrc----1160">
<h1 id="----npmrc----1161">
<span>npmrc</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">The npm config files</span>
</header>
@ -216,9 +216,9 @@ consistent across updates. Set fields in here using the <code>./configure</code
script that comes with npm. This is primarily for distribution maintainers
to override default configs in a standard and consistent manner.</p>
<h3 id="auth-related-configuration">Auth related configuration</h3>
<p>The settings <code>_auth</code>, <code>_authToken</code>, <code>username</code> and <code>_password</code> must all be
scoped to a specific registry. This ensures that <code>npm</code> will never send
credentials to the wrong host.</p>
<p>The settings <code>_auth</code>, <code>_authToken</code>, <code>username</code>, <code>_password</code>, <code>certfile</code>,
and <code>keyfile</code> must all be scoped to a specific registry. This ensures that
<code>npm</code> will never send credentials to the wrong host.</p>
<p>The full list is:</p>
<ul>
<li><code>_auth</code> (base64 authentication string)</li>
@ -227,6 +227,7 @@ credentials to the wrong host.</p>
<li><code>_password</code></li>
<li><code>email</code></li>
<li><code>cafile</code> (path to certificate authority file)</li>
<li><code>certfile</code> (path to certificate file)</li>
<li><code>keyfile</code> (path to key file)</li>
</ul>
<p>In order to scope these values, they must be prefixed by a URI fragment.

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----packagejson----1160">
<h1 id="----packagejson----1161">
<span>package.json</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Specifics of npm's package.json handling</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----package-lockjson----1160">
<h1 id="----package-lockjson----1161">
<span>package-lock.json</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">A manifestation of the manifest</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----config----1160">
<h1 id="----config----1161">
<span>config</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">More than you probably want to know about npm configuration</span>
</header>
@ -1495,9 +1495,9 @@ command line.</p>
<li>Default: null</li>
<li>Type: null or String</li>
<li>DEPRECATED: <code>key</code> and <code>cert</code> are no longer used for most registry
operations. Use registry scoped <code>keyfile</code> and <code>cafile</code> instead. Example:
operations. Use registry scoped <code>keyfile</code> and <code>certfile</code> instead. Example:
//other-registry.tld/:keyfile=/path/to/key.pem
//other-registry.tld/:cafile=/path/to/cert.crt</li>
//other-registry.tld/:certfile=/path/to/cert.crt</li>
</ul>
<p>A client certificate to pass when accessing the registry. Values should be
in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with
@ -1505,8 +1505,8 @@ newlines replaced by the string "\n". For example:</p>
<pre><code class="language-ini">cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
</code></pre>
<p>It is <em>not</em> the path to a certificate file, though you can set a
registry-scoped "cafile" path like
"//other-registry.tld/:cafile=/path/to/cert.pem".</p>
registry-scoped "certfile" path like
"//other-registry.tld/:certfile=/path/to/cert.pem".</p>
<h4 id="dev"><code>dev</code></h4>
<ul>
<li>Default: false</li>
@ -1570,9 +1570,9 @@ on deeper dependencies. Sets <code>--install-strategy=shallow</code>.</p>
<li>Default: null</li>
<li>Type: null or String</li>
<li>DEPRECATED: <code>key</code> and <code>cert</code> are no longer used for most registry
operations. Use registry scoped <code>keyfile</code> and <code>cafile</code> instead. Example:
operations. Use registry scoped <code>keyfile</code> and <code>certfile</code> instead. Example:
//other-registry.tld/:keyfile=/path/to/key.pem
//other-registry.tld/:cafile=/path/to/cert.crt</li>
//other-registry.tld/:certfile=/path/to/cert.crt</li>
</ul>
<p>A client key to pass when accessing the registry. Values should be in PEM
format with newlines replaced by the string "\n". For example:</p>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----dependency-selector-syntax--querying----1160">
<h1 id="----dependency-selector-syntax--querying----1161">
<span>Dependency Selector Syntax &amp; Querying</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Dependency Selector Syntax &amp; Querying</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----developers----1160">
<h1 id="----developers----1161">
<span>developers</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Developer Guide</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----logging----1160">
<h1 id="----logging----1161">
<span>Logging</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Why, What &amp; How We Log</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----orgs----1160">
<h1 id="----orgs----1161">
<span>orgs</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Working with Teams &amp; Orgs</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----package-spec----1160">
<h1 id="----package-spec----1161">
<span>package-spec</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Package name specifier</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----registry----1160">
<h1 id="----registry----1161">
<span>registry</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">The JavaScript Package Registry</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----removal----1160">
<h1 id="----removal----1161">
<span>removal</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Cleaning the Slate</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----scope----1160">
<h1 id="----scope----1161">
<span>scope</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Scoped packages</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----scripts----1160">
<h1 id="----scripts----1161">
<span>scripts</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">How npm handles the "scripts" field</span>
</header>

View File

@ -141,9 +141,9 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="----workspaces----1160">
<h1 id="----workspaces----1161">
<span>workspaces</span>
<span class="version">@11.6.0</span>
<span class="version">@11.6.1</span>
</h1>
<span class="description">Working with workspaces</span>
</header>

View File

@ -1,4 +1,4 @@
.TH "NPM-ACCESS" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-ACCESS" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-access\fR - Set access level on published packages
.SS "Synopsis"
@ -103,7 +103,7 @@ The base URL of the npm registry.
.SS "See Also"
.RS 0
.IP \(bu 4
\fB\fBlibnpmaccess\fR\fR \fI\(lahttps://npm.im/libnpmaccess\(ra\fR
\fB\[rs]fBlibnpmaccess\[rs]fR\fR \fI\(lahttps://npm.im/libnpmaccess\(ra\fR
.IP \(bu 4
npm help team
.IP \(bu 4

View File

@ -1,4 +1,4 @@
.TH "NPM-ADDUSER" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-ADDUSER" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-adduser\fR - Add a registry user account
.SS "Synopsis"

View File

@ -1,4 +1,4 @@
.TH "NPM-AUDIT" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-AUDIT" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-audit\fR - Run a security audit
.SS "Synopsis"
@ -102,7 +102,7 @@ As of version 7, npm uses the much faster \fBBulk Advisory\fR endpoint to optimi
.P
npm will generate a JSON payload with the name and list of versions of each package in the tree, and POST it to the default configured registry at the path \fB/-/npm/v1/security/advisories/bulk\fR.
.P
Any packages in the tree that do not have a \fBversion\fR field in their package.json file will be ignored. If any \fB--omit\fR options are specified (either via the \fB\fB--omit\fR config\fR \fI\(la/using-npm/config#omit\(ra\fR, or one of the shorthands such as \fB--production\fR, \fB--only=dev\fR, and so on), then packages will be omitted from the submitted payload as appropriate.
Any packages in the tree that do not have a \fBversion\fR field in their package.json file will be ignored. If any \fB--omit\fR options are specified (either via the \fB\[rs]fB--omit\[rs]fR config\fR \fI\(la/using-npm/config#omit\(ra\fR, or one of the shorthands such as \fB--production\fR, \fB--only=dev\fR, and so on), then packages will be omitted from the submitted payload as appropriate.
.P
If the registry responds with an error, or with an invalid response, then npm will attempt to load advisory data from the \fBQuick Audit\fR endpoint.
.P
@ -138,7 +138,7 @@ However, in practice, this resulted in audits often failing to properly detect m
This scrubbing has been removed from npm as of version 7.
.SS "Calculating Meta-Vulnerabilities and Remediations"
.P
npm uses the \fB\fB@npmcli/metavuln-calculator\fR\fR \fI\(lahttp://npm.im/@npmcli/metavuln-calculator\(ra\fR module to turn a set of security advisories into a set of "vulnerability" objects. A "meta-vulnerability" is a dependency that is vulnerable by virtue of dependence on vulnerable versions of a vulnerable package.
npm uses the \fB\[rs]fB@npmcli/metavuln-calculator\[rs]fR\fR \fI\(lahttp://npm.im/@npmcli/metavuln-calculator\(ra\fR module to turn a set of security advisories into a set of "vulnerability" objects. A "meta-vulnerability" is a dependency that is vulnerable by virtue of dependence on vulnerable versions of a vulnerable package.
.P
For example, if the package \fBfoo\fR is vulnerable in the range \fB>=1.0.2
<2.0.0\fR, and the package \fBbar\fR depends on \fBfoo@^1.1.0\fR, then that version of \fBbar\fR can only be installed by installing a vulnerable version of \fBfoo\fR. In this case, \fBbar\fR is a "metavulnerability".
@ -150,7 +150,7 @@ If the chain of metavulnerabilities extends all the way to the root project, and
.P
The \fBnpm audit\fR command will exit with a 0 exit code if no vulnerabilities were found. The \fBnpm audit fix\fR command will exit with 0 exit code if no vulnerabilities are found \fIor\fR if the remediation is able to successfully fix all vulnerabilities.
.P
If vulnerabilities were found the exit code will depend on the \fB\fBaudit-level\fR config\fR \fI\(la/using-npm/config#audit-level\(ra\fR.
If vulnerabilities were found the exit code will depend on the \fB\[rs]fBaudit-level\[rs]fR config\fR \fI\(la/using-npm/config#audit-level\(ra\fR.
.SS "Examples"
.P
Scan your project for vulnerabilities and automatically install any compatible updates to vulnerable dependencies:

View File

@ -1,4 +1,4 @@
.TH "NPM-BUGS" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-BUGS" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-bugs\fR - Report bugs for a package in a web browser
.SS "Synopsis"
@ -12,7 +12,7 @@ alias: issues
.RE
.SS "Description"
.P
This command tries to guess at the likely location of a package's bug tracker URL or the \fBmailto\fR URL of the support email, and then tries to open it using the \fB\fB--browser\fR config\fR \fI\(la/using-npm/config#browser\(ra\fR param. If no package name is provided, it will search for a \fBpackage.json\fR in the current folder and use the \fBname\fR property.
This command tries to guess at the likely location of a package's bug tracker URL or the \fBmailto\fR URL of the support email, and then tries to open it using the \fB\[rs]fB--browser\[rs]fR config\fR \fI\(la/using-npm/config#browser\(ra\fR param. If no package name is provided, it will search for a \fBpackage.json\fR in the current folder and use the \fBname\fR property.
.SS "Configuration"
.SS "\fBbrowser\fR"
.RS 0

View File

@ -1,4 +1,4 @@
.TH "NPM-CACHE" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-CACHE" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-cache\fR - Manipulates packages cache
.SS "Synopsis"
@ -43,7 +43,7 @@ info: Get detailed information about given entries in the npx cache.
.SS "Details"
.P
npm stores cache data in an opaque directory within the configured \fBcache\fR, named \fB_cacache\fR. This directory is a \fB\fBcacache\fR\fR \fI\(lahttp://npm.im/cacache\(ra\fR-based content-addressable cache that stores all http request data as well as other package-related data. This directory is primarily accessed through \fBpacote\fR, the library responsible for all package fetching as of npm@5.
npm stores cache data in an opaque directory within the configured \fBcache\fR, named \fB_cacache\fR. This directory is a \fB\[rs]fBcacache\[rs]fR\fR \fI\(lahttp://npm.im/cacache\(ra\fR-based content-addressable cache that stores all http request data as well as other package-related data. This directory is primarily accessed through \fBpacote\fR, the library responsible for all package fetching as of npm@5.
.P
All data that passes through the cache is fully verified for integrity on both insertion and extraction. Cache corruption will either trigger an error, or signal to \fBpacote\fR that the data must be refetched, which it will do automatically. For this reason, it should never be necessary to clear the cache for any reason other than reclaiming disk space, thus why \fBclean\fR now requires \fB--force\fR to run.
.P

View File

@ -1,4 +1,4 @@
.TH "NPM-CI" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-CI" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-ci\fR - Clean install a project
.SS "Synopsis"

View File

@ -1,4 +1,4 @@
.TH "NPM-COMPLETION" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-COMPLETION" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-completion\fR - Tab Completion for npm
.SS "Synopsis"

View File

@ -1,4 +1,4 @@
.TH "NPM-CONFIG" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-CONFIG" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-config\fR - Manage the npm configuration files
.SS "Synopsis"
@ -38,7 +38,7 @@ npm set key=value \[lB]key=value...\[rB]
.fi
.RE
.P
Sets each of the config keys to the value provided. Modifies the user configuration file unless \fB\fBlocation\fR\fR \fI\(la/commands/npm-config#location\(ra\fR is passed.
Sets 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.
.P
If value is omitted, the key will be removed from your config file entirely.
.P

View File

@ -1,4 +1,4 @@
.TH "NPM-DEDUPE" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-DEDUPE" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-dedupe\fR - Reduce duplication in the package tree
.SS "Synopsis"

View File

@ -1,4 +1,4 @@
.TH "NPM-DEPRECATE" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-DEPRECATE" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-deprecate\fR - Deprecate a version of a package
.SS "Synopsis"

View File

@ -1,4 +1,4 @@
.TH "NPM-DIFF" "1" "September 2025" "NPM@11.6.0" ""
.TH "NPM-DIFF" "1" "September 2025" "NPM@11.6.1" ""
.SH "NAME"
\fBnpm-diff\fR - The registry diff command
.SS "Synopsis"
@ -64,7 +64,7 @@ This workflow provides a handy way for package authors to see what package-track
.IP \(bu 4
\fBnpm diff --diff=<pkg-name>\fR (in a package directory):
.P
When using a single package name (with no version or tag specifier) as an argument, \fBnpm diff\fR will work in a similar way to \fB\fBnpm-outdated\fR\fR \fI\(lanpm-outdated\(ra\fR and reach for the registry to figure out what current published version of the package named \fB<pkg-name>\fR will satisfy its dependent declared semver-range. Once that specific version is known \fBnpm diff\fR will print diff patches comparing the current version of \fB<pkg-name>\fR found in the local file system with that specific version returned by the registry.
When using a single package name (with no version or tag specifier) as an argument, \fBnpm diff\fR will work in a similar way to \fB\[rs]fBnpm-outdated\[rs]fR\fR \fI\(lanpm-outdated\(ra\fR and reach for the registry to figure out what current published version of the package named \fB<pkg-name>\fR will satisfy its dependent declared semver-range. Once that specific version is known \fBnpm diff\fR will print diff patches comparing the current version of \fB<pkg-name>\fR found in the local file system with that specific version returned by the registry.
.P
Given a package named \fBabbrev\fR that is currently installed:
.P

Some files were not shown because too many files have changed in this diff Show More