deps: upgrade npm to 11.6.2

PR-URL: #60168
Reviewed-By: Jordan Harband <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Ulises Gascón <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

Author: npm-cli-bot

deps/npm/README.md

@@ -36,13 +36,12 @@ npm <command>
 * [**RFCs**](https://github.com/npm/rfcs) - Contribute ideas & specifications for the API/design of the npm CLI
 * [**Service Status**](https://status.npmjs.org/) - Monitor the current status & see incident reports for the website & registry
 * [**Project Status**](https://npm.github.io/statusboard/) - See the health of all our maintained OSS projects in one view
-* [**Events Calendar**](https://calendar.google.com/calendar/u/0/embed?src=npmjs.com_oonluqt8oftrt0vmgrfbg6q6go@group.calendar.google.com) - Keep track of our Open RFC calls, releases, meetups, conferences & more
-* [**Support**](https://www.npmjs.com/support) - Experiencing problems with the **npm** [website](https://npmjs.com) or [registry](https://registry.npmjs.org)? File a ticket [here](https://www.npmjs.com/support)
+* [**Support**](https://www.npmjs.com/support) - Experiencing problems with the **npm** [website](https://npmjs.com) or [registry](https://registry.npmjs.org)? [File a ticket](https://www.npmjs.com/support)
 
 ### Acknowledgments
 
 * `npm` is configured to use the **npm Public Registry** at [https://registry.npmjs.org](https://registry.npmjs.org) by default; Usage of this registry is subject to **Terms of Use** available at [https://npmjs.com/policies/terms](https://npmjs.com/policies/terms)
-* You can configure `npm` to use any other compatible registry you prefer. You can read more about configuring third-party registries [here](https://docs.npmjs.com/cli/v7/using-npm/registry)
+* You can configure `npm` to use any other compatible registry you prefer. You can read more about [configuring third-party registries](https://docs.npmjs.com/cli/v7/using-npm/registry)
 
 ### FAQ on Branding
 

deps/npm/docs/content/commands/npm-access.md

@@ -22,56 +22,28 @@ Note: This command is unaware of workspaces.
 
 Used to set access controls on private packages.
 
-For all of the subcommands, `npm access` will perform actions on the packages
-in the current working directory if no package name is passed to the
-subcommand.
+For all of the subcommands, `npm access` will perform actions on the packages in the current working directory if no package name is passed to the subcommand.
 
-* public / restricted (deprecated):
-  Set a package to be either publicly accessible or restricted.
-
-* grant / revoke (deprecated):
-  Add or remove the ability of users and teams to have read-only or read-write
-  access to a package.
-
-* 2fa-required / 2fa-not-required (deprecated):
-  Configure whether a package requires that anyone publishing it have two-factor
-  authentication enabled on their account.
-
-* ls-packages (deprecated):
-  Show all of the packages a user or a team is able to access, along with the
-  access level, except for read-only public packages (it won't print the whole
-  registry listing)
-
-* ls-collaborators (deprecated):
-  Show all of the access privileges for a package. Will only show permissions
-  for packages to which you have at least read access. If `<user>` is passed in,
-  the list is filtered only to teams _that_ user happens to belong to.
-
-* edit (not implemented)
+* grant / revoke:
+  Add or remove the ability of users and teams to have read-only or read-write access to a package.
 
 ### Details
 
-`npm access` always operates directly on the current registry, configurable
-from the command line using `--registry=<registry url>`.
+`npm access` always operates directly on the current registry, configurable from the command line using `--registry=<registry url>`.
 
 Unscoped packages are *always public*.
 
-Scoped packages *default to restricted*, but you can either publish them as
-public using `npm publish --access=public`, or set their access as public using
-`npm access public` after the initial publish.
+Scoped packages *default to restricted*, but you can either publish them as public using `npm publish --access=public`, or set their access as public using `npm access set status=public` after the initial publish.
 
 You must have privileges to set the access of a package:
 
 * You are an owner of an unscoped or scoped package.
 * You are a member of the team that owns a scope.
-* You have been given read-write privileges for a package, either as a member
-  of a team or directly as an owner.
+* You have been given read-write privileges for a package, either as a member of a team or directly as an owner.
 
-If you have two-factor authentication enabled then you'll be prompted to provide a second factor, or may use the `--otp=...` option to specify it on
-the command line.
+If you have two-factor authentication enabled then you'll be prompted to provide a second factor, or may use the `--otp=...` option to specify it on the command line.
 
-If your account is not paid, then attempts to publish scoped packages will
-fail with an HTTP 402 status code (logically enough), unless you use
+If your account is not paid, then attempts to publish scoped packages will fail with an HTTP 402 status code (logically enough), unless you use
 `--access=public`.
 
 Management of teams and team memberships is done with the `npm team` command.
@@ -85,8 +57,8 @@ Management of teams and team memberships is done with the `npm team` command.
 
 Whether or not to output JSON data, rather than the normal output.
 
-* In `npm pkg set` it enables parsing set values with JSON.parse() before
-  saving them to your `package.json`.
+* In `npm pkg set` it enables parsing set values with JSON.parse()
+  before saving them to your `package.json`.
 
 Not supported by all npm commands.
 
@@ -97,11 +69,12 @@ Not supported by all npm commands.
 * Default: null
 * Type: null or String
 
-This is a one-time password from a two-factor authenticator. It's needed
-when publishing or changing package permissions with `npm access`.
+This is a one-time password from a two-factor authenticator. It's
+needed 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.
+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.
 
 
 

deps/npm/docs/content/commands/npm-adduser.md

@@ -16,14 +16,13 @@ Note: This command is unaware of workspaces.
 
 ### Description
 
-Create a new user in the specified registry, and save the credentials to
-the `.npmrc` file. If no registry is specified, the default registry
-will be used (see [`registry`](/using-npm/registry)).
+Create a new user in the specified registry, and save the credentials to the `.npmrc` file.
+If no registry is specified, the default registry will be used (see [`registry`](/using-npm/registry)).
 
-When you run `npm adduser`, the CLI automatically generates a legacy token of `publish` type. For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens).
+When you run `npm adduser`, the CLI automatically generates a legacy token of `publish` type.
+For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens).
 
-When using `legacy` for your `auth-type`, the username, password, and
-email are read in from prompts.
+When using `legacy` for your `auth-type`, the username, password, and email are read in from prompts.
 
 ### Configuration
 
@@ -72,8 +71,8 @@ npm init --scope=@foo --yes
 * Default: "web"
 * Type: "legacy" or "web"
 
-What authentication strategy to use with `login`. Note that if an `otp`
-config is given, this value will always be set to `legacy`.
+What authentication strategy to use with `login`. Note that if an
+`otp` config is given, this value will always be set to `legacy`.