Update working-with-the-npm-registry.md#23095
Conversation
Command line update based on my experiment. Using the command without "--auth-type=legacy" will result in "Web login not supported" error.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
This comment was marked as spam.
This comment was marked as spam.
|
Close for now and will create new one. |
Document and sample command update based on my testing/experiment. With npm v9, using the command without "--auth-type=legacy" will result in "Web login not supported" error.
Why:
Closes ISSUE
What's being changed (if available, include any code snippets, screenshots, or gifs):
Added instruction "You will be prompted with username, password entering, and please note to use your personal access token as the password upon prompt."
Updated command from
'''
$ npm login --scope=@owner --registry=https://HOSTNAME/_registry/npm/
Check off the following: