Repository navigation
Re-verify npm auth after auto-login - #800
Merged
Merged
Conversation
After auto-running `npm login`, re-check `npm whoami` and fail with a clear, actionable error if still not authenticated, instead of silently continuing to a second whoami check that re-throws a generic message. The common cause is a project-level `.npmrc` holding a stale or revoked token that overrides the session token `npm login` writes to the user `.npmrc`. Fixes #795
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
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.
After auto-running
npm login, re-checknpm whoamiand fail with a clear, actionable error if still not authenticated, instead of silently continuing to a second whoami check that re-throws a generic message. The common cause is a project-level.npmrcholding a stale or revoked token that overrides the session tokennpm loginwrites to the user.npmrc.Fixes #795