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 scope is provided #1994

Closed
ohardy opened this issue Oct 20, 2020 · 2 comments
Closed

[BUG] npm 7.x ignores publishConfig.registry scope is provided #1994

ohardy opened this issue Oct 20, 2020 · 2 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release

Comments

@ohardy
Copy link

ohardy commented Oct 20, 2020

Current Behavior:

npm publish does not follow publishConfig.registry scoped registry configured in publishConfig.registry

Expected Behavior:

npm publish publish to defined scoped publishConfig.registry

Steps To Reproduce:

  1. Install npm@latest-7
  2. Set publishConfig.registry IE: "publishConfig": { "@my-scope:registry": "https://..." }
  3. Run npm publish

Environment:

OS: Max OS 10.15.7
Node: 14.14.0
npm: 7.0.2

@ohardy ohardy 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 Oct 20, 2020
@ohardy ohardy changed the title [BUG] npm 7.x ignores publishConfig.registry when --tag is provided [BUG] npm 7.x ignores publishConfig.registry scope is provided Oct 20, 2020
@isaacs
Copy link
Contributor

isaacs commented Nov 5, 2020

Fixed in latest release.

@isaacs isaacs closed this as completed Nov 5, 2020
@darcyclarke darcyclarke added this to the OSS - Sprint 19 milestone Nov 16, 2020
@thw0rted
Copy link

Is it possible that the fix for this could have re-broken #1937 ? As I commented there, as of 7.3.0, publish is ignoring my publishConfig.registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

No branches or pull requests

4 participants