Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] npm login with scope create .npmrc without @scope:registry=... #3292

Closed
1 task done
hajekj14 opened this issue May 23, 2021 · 2 comments
Closed
1 task done

[BUG] npm login with scope create .npmrc without @scope:registry=... #3292

hajekj14 opened this issue May 23, 2021 · 2 comments
Assignees
Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release

Comments

@hajekj14
Copy link

hajekj14 commented May 23, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

npm login --registry=http://reg.example.com --scope=@myco

create ~/.npmrc

//reg.example.com/:_authToken="token"

Expected Behavior

npm login --registry=http://reg.example.com --scope=@myco

create ~/.npmrc

@myco:registry=https://reg.example.com/
//reg.example.com/:_authToken="token"

Steps To Reproduce

  1. In this environment...
  2. With this config...
  3. Run '...'
  4. See error...

Environment

  • OS: Linux & Win in general
  • Node:
  • npm: 7.8.0
@hajekj14 hajekj14 added Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release labels May 23, 2021
@syakovyn
Copy link

syakovyn commented Jun 1, 2021

I can confirm the bug still exists on 7.13.0.
Version 7.0.10 is not affected so it looks like a regression.

@wraithgar wraithgar added Priority 1 high priority issue and removed Needs Triage needs review for next steps labels Jun 7, 2021
@wraithgar wraithgar self-assigned this Jun 7, 2021
@tsuilouis
Copy link

I am using npm v7.20.3 at work and I've encountered this exact same problem. I see that the fix was released in v7.17.0 so I'm wondering if something occurred in between to cause a regression. The problem looks to have even made it all the way to v8.1.4 based on the latest mention.

@hajekj14 @syakovyn were either of you able to verify that the behaviour works as expected after v7.17.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

No branches or pull requests

4 participants