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 7.x ignores publishConfig.registry #2525

Closed
MikaelX opened this issue Jan 21, 2021 · 1 comment
Closed

[BUG] npm 7.x ignores publishConfig.registry #2525

MikaelX opened this issue Jan 21, 2021 · 1 comment
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

@MikaelX
Copy link

MikaelX commented Jan 21, 2021

Current Behavior:
npm publish does not follow publishConfig.registry, if registry is .npmrc it will try to publish to that, if not npm.org.

Expected Behavior:
npm publish publish to defined publishConfig.registry as it did in 6.x.

Steps To Reproduce:
Install npm@7
Set publishConfig.registry IE: "publishConfig": { "registry": "https://..." }
Run npm publish
Environment:
OS: Mac OS BigSur
Node: 15.4.0
npm: 7.4.3

Same bug as
Bug 1937

Reverting back to npm@6 will solve the issue

@MikaelX MikaelX 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 Jan 21, 2021
@MikaelX MikaelX changed the title [BUG] <title> [BUG] npm 7.x ignores publishConfig.registry Jan 21, 2021
@darcyclarke darcyclarke added Priority 1 high priority issue and removed Needs Triage needs review for next steps labels Feb 2, 2021
@wraithgar
Copy link
Member

#1937 has been fixed, and the related ENEEDAUTH bug is tracked in #2567 and will be closed by #2602

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