Skip to content

Update working-with-the-npm-registry.md#23095

Closed
zizyan wants to merge 1 commit intogithub:mainfrom
zizyan:patch-1
Closed

Update working-with-the-npm-registry.md#23095
zizyan wants to merge 1 commit intogithub:mainfrom
zizyan:patch-1

Conversation

@zizyan
Copy link
Copy Markdown
Contributor

@zizyan zizyan commented Jan 9, 2023

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/

Username: USERNAME
Password: TOKEN
Email: PUBLIC-EMAIL-ADDRESS
'''
to
'''
npm login --scope=@owner --registry=https://HOSTNAME/_registry/npm/ --auth-type=legacy
'''

Check off the following:

  • I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Command line update based on my experiment. Using the command without "--auth-type=legacy" will result in "Web login not supported" error.
@welcome
Copy link
Copy Markdown

welcome Bot commented Jan 9, 2023

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.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jan 9, 2023
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 9, 2023

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 that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You 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.

Source Preview Production What Changed
packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md fpt
ghec
ghes@ 3.7 3.6 3.5 3.4 3.3
ghae
fpt
ghec
ghes@ 3.7 3.6 3.5 3.4 3.3
ghae

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

@ahmad054480

This comment was marked as spam.

@zizyan zizyan closed this Jan 9, 2023
@zizyan
Copy link
Copy Markdown
Contributor Author

zizyan commented Jan 9, 2023

Close for now and will create new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Packages: Working with the npm registry: missing npm login argument for npm v9

2 participants