docs: clarify legacy token creation in npm login and adduser commands #8226
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
owlstronaut
requested changes
Apr 14, 2025
| @@ -14,6 +14,8 @@ 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). | |||
There was a problem hiding this comment.
Suggested change
| 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). |
| @@ -14,6 +14,8 @@ Verify a 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 [`config`](/using-npm/config)). | |||
|
|
|||
| When you run `npm login`, the CLI automatically generates a legacy token of publish type. For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens). | |||
There was a problem hiding this comment.
Suggested change
| When you run `npm login`, 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 login`, the CLI automatically generates a legacy token of `publish` type. For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens). |
owlstronaut
approved these changes
Apr 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is simple PR for adjust
npm loginandnpm adduserdoc.Problem Description:
When using
npm login/npm adduser, users are not aware that this command generates a legacy token with publish permissions. This information is not evident in thenpm login/npm addusercli documentation.After a while searching. found that this context and detail hiding in the About legacy tokens documentation.
Solution:
Add a clear description in the
npm login/npm adduserdocumentation in this PR so that users can understand publish token would be created afternpm loginin the future.References
Related to this PR: npm/documentation#1550