github
Packages: Working with the npm registry: missing npm login argument for npm v9
Code of Conduct
- [X] I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#authenticating-to-github-packages
What part(s) of the article would you like to see updated?
Under "Authenticating with a personal access token", the npm login command is described. The instructions do not work with npm v9, as the default authentication method has changed to "web" and GitHub uses the "legacy" method. The --auth-type=legacy argument is required to solve this. See https://docs.npmjs.com/cli/v9/commands/npm-login for the CLI ref and https://www.jfrog.com/confluence/display/JFROG/npm+Registry for the Artifactory docs regarding this issue.
Additional information
No response
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
![welcome[bot] avatar](https://avatars.githubusercontent.com/in/4141?v=4 "Published by a pub.dev verified publisher"){kind=small}
Dihantar daripada telefon saya-------- Mesej asal --------Daripada: "welcome[bot]" @.>Tarikh: Isn, 21 Nov 2022, 9:23 PTGKepada: github/docs @.>Sk: Subscribed @.***>Tajuk: Re: [github/docs] Packages: Working with the npm registry: missing npm login argument for npm v9 (Issue #22199) Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
@boraozgen Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:
Future docs reviewer: The npm and Packages teams have confirmed this change makes sense. See link in notes.
Hi @boraozgen, thank you for opening this issue! We've checked with the product team and your description makes sense. You or anyone else is welcome to create a PR to address this. 🔧