deps: upgrade npm to 11.6.2 · nodejs/node@1b22f60 · GitHub
Skip to content

Commit 1b22f60

Browse files
npm-cli-botnpm-cli-bot
authored
deps: upgrade npm to 11.6.2
PR-URL: #60168 Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent aef3fc3 commit 1b22f60

370 files changed

Lines changed: 8540 additions & 11114 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎deps/npm/README.md‎

Lines changed: 2 additions & 3 deletions

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

Lines changed: 15 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -22,56 +22,28 @@ Note: This command is unaware of workspaces.
2222
2323
Used to set access controls on private packages.
2424
25-
For all of the subcommands, `npm access` will perform actions on the packages
26-
in the current working directory if no package name is passed to the
27-
subcommand.
25+
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.
2826
29-
* public / restricted (deprecated):
30-
Set a package to be either publicly accessible or restricted.
31-
32-
* grant / revoke (deprecated):
33-
Add or remove the ability of users and teams to have read-only or read-write
34-
access to a package.
35-
36-
* 2fa-required / 2fa-not-required (deprecated):
37-
Configure whether a package requires that anyone publishing it have two-factor
38-
authentication enabled on their account.
39-
40-
* ls-packages (deprecated):
41-
Show all of the packages a user or a team is able to access, along with the
42-
access level, except for read-only public packages (it won't print the whole
43-
registry listing)
44-
45-
* ls-collaborators (deprecated):
46-
Show all of the access privileges for a package. Will only show permissions
47-
for packages to which you have at least read access. If `<user>` is passed in,
48-
the list is filtered only to teams _that_ user happens to belong to.
49-
50-
* edit (not implemented)
27+
* grant / revoke:
28+
Add or remove the ability of users and teams to have read-only or read-write access to a package.
5129
5230
### Details
5331
54-
`npm access` always operates directly on the current registry, configurable
55-
from the command line using `--registry=<registry url>`.
32+
`npm access` always operates directly on the current registry, configurable from the command line using `--registry=<registry url>`.
5633
5734
Unscoped packages are *always public*.
5835
59-
Scoped packages *default to restricted*, but you can either publish them as
60-
public using `npm publish --access=public`, or set their access as public using
61-
`npm access public` after the initial publish.
36+
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.
6237
6338
You must have privileges to set the access of a package:
6439
6540
* You are an owner of an unscoped or scoped package.
6641
* You are a member of the team that owns a scope.
67-
* You have been given read-write privileges for a package, either as a member
68-
of a team or directly as an owner.
42+
* You have been given read-write privileges for a package, either as a member of a team or directly as an owner.
6943
70-
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
71-
the command line.
44+
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.
7245
73-
If your account is not paid, then attempts to publish scoped packages will
74-
fail with an HTTP 402 status code (logically enough), unless you use
46+
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
7547
`--access=public`.
7648
7749
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.
8557
8658
Whether or not to output JSON data, rather than the normal output.
8759
88-
* In `npm pkg set` it enables parsing set values with JSON.parse() before
89-
saving them to your `package.json`.
60+
* In `npm pkg set` it enables parsing set values with JSON.parse()
61+
before saving them to your `package.json`.
9062
9163
Not supported by all npm commands.
9264
@@ -97,11 +69,12 @@ Not supported by all npm commands.
9769
* Default: null
9870
* Type: null or String
9971
100-
This is a one-time password from a two-factor authenticator. It's needed
101-
when publishing or changing package permissions with `npm access`.
72+
This is a one-time password from a two-factor authenticator. It's
73+
needed when publishing or changing package permissions with `npm
74+
access`.
10275
103-
If not set, and a registry response fails with a challenge for a one-time
104-
password, npm will prompt on the command line for one.
76+
If not set, and a registry response fails with a challenge for a
77+
one-time password, npm will prompt on the command line for one.
10578
10679
10780

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

Lines changed: 7 additions & 8 deletions

0 commit comments

Comments
 (0)