{{ message }}
Commit a56aa9f
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 b0da3b9 commit a56aa9f
370 files changed
Lines changed: 8540 additions & 11114 deletions
File tree
- deps/npm
- docs
- content
- commands
- configuring-npm
- using-npm
- lib
- output
- commands
- configuring-npm
- using-npm
- lib
- cli
- commands
- utils
- man
- man1
- man5
- man7
- node_modules
- @npmcli
- arborist
- bin
- lib
- arborist
- config
- lib
- definitions
- @sigstore/sign
- dist/util
- ci-info
- cidr-regex
- hosted-git-info
- lib
- is-cidr
- libnpmaccess
- lib
- libnpmdiff
- libnpmexec
- lib
- libnpmfund
- libnpmpack
- libnpmpublish
- libnpmversion
- lru-cache
- dist
- commonjs
- esm
- normalize-package-data
- lib
- npm-package-arg
- lib
- npm-packlist
- lib
- semver
- classes
- internal
- tap-snapshots/test/lib
- commands
- utils
- test/lib
- cli
- commands
- utils
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -36,13 +36,12 @@ npm <command> | |||
| 36 | 36 | * [**RFCs**](https://github.com/npm/rfcs) - Contribute ideas & specifications for the API/design of the npm CLI | |
| 37 | 37 | * [**Service Status**](https://status.npmjs.org/) - Monitor the current status & see incident reports for the website & registry | |
| 38 | 38 | * [**Project Status**](https://npm.github.io/statusboard/) - See the health of all our maintained OSS projects in one view | |
| 39 | - * [**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 | ||
| 40 | - * [**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) | ||
| 39 | + * [**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) | ||
| 41 | 40 | ||
| 42 | 41 | ### Acknowledgments | |
| 43 | 42 | ||
| 44 | 43 | * `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) | |
| 45 | - * 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) | ||
| 44 | + * 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) | ||
| 46 | 45 | ||
| 47 | 46 | ### FAQ on Branding | |
| 48 | 47 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -22,56 +22,28 @@ Note: This command is unaware of workspaces. | |||
| 22 | 22 | ||
| 23 | 23 | Used to set access controls on private packages. | |
| 24 | 24 | ||
| 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. | ||
| 28 | 26 | ||
| 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. | ||
| 51 | 29 | ||
| 52 | 30 | ### Details | |
| 53 | 31 | ||
| 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>`. | ||
| 56 | 33 | ||
| 57 | 34 | Unscoped packages are *always public*. | |
| 58 | 35 | ||
| 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. | ||
| 62 | 37 | ||
| 63 | 38 | You must have privileges to set the access of a package: | |
| 64 | 39 | ||
| 65 | 40 | * You are an owner of an unscoped or scoped package. | |
| 66 | 41 | * 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. | ||
| 69 | 43 | ||
| 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. | ||
| 72 | 45 | ||
| 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 | ||
| 75 | 47 | `--access=public`. | |
| 76 | 48 | ||
| 77 | 49 | 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. | |||
| 85 | 57 | ||
| 86 | 58 | Whether or not to output JSON data, rather than the normal output. | |
| 87 | 59 | ||
| 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`. | ||
| 90 | 62 | ||
| 91 | 63 | Not supported by all npm commands. | |
| 92 | 64 | ||
@@ -97,11 +69,12 @@ Not supported by all npm commands. | |||
| 97 | 69 | * Default: null | |
| 98 | 70 | * Type: null or String | |
| 99 | 71 | ||
| 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`. | ||
| 102 | 75 | ||
| 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. | ||
| 105 | 78 | ||
| 106 | 79 | ||
| 107 | 80 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -16,14 +16,13 @@ Note: This command is unaware of workspaces. | |||
| 16 | 16 | ||
| 17 | 17 | ### Description | |
| 18 | 18 | ||
| 19 | - Create a new user in the specified registry, and save the credentials to | ||
| 20 | - the `.npmrc` file. If no registry is specified, the default registry | ||
| 21 | - will be used (see [`registry`](/using-npm/registry)). | ||
| 19 | + Create a new user in the specified registry, and save the credentials to the `.npmrc` file. | ||
| 20 | + If no registry is specified, the default registry will be used (see [`registry`](/using-npm/registry)). | ||
| 22 | 21 | ||
| 23 | - 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). | ||
| 22 | + When you run `npm adduser`, the CLI automatically generates a legacy token of `publish` type. | ||
| 23 | + For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens). | ||
| 24 | 24 | ||
| 25 | - When using `legacy` for your `auth-type`, the username, password, and | ||
| 26 | - email are read in from prompts. | ||
| 25 | + When using `legacy` for your `auth-type`, the username, password, and email are read in from prompts. | ||
| 27 | 26 | ||
| 28 | 27 | ### Configuration | |
| 29 | 28 | ||
@@ -72,8 +71,8 @@ npm init --scope=@foo --yes | |||
| 72 | 71 | * Default: "web" | |
| 73 | 72 | * Type: "legacy" or "web" | |
| 74 | 73 | ||
| 75 | - What authentication strategy to use with `login`. Note that if an `otp` | ||
| 76 | - config is given, this value will always be set to `legacy`. | ||
| 74 | + What authentication strategy to use with `login`. Note that if an | ||
| 75 | + `otp` config is given, this value will always be set to `legacy`. | ||
| 77 | 76 | ||
| 78 | 77 | ||
| 79 | 78 | ||
0 commit comments