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

--registry should have higher priority over publishConfig.registry #6423

Closed
wants to merge 1 commit into from

Conversation

Fer0x
Copy link
Contributor

@Fer0x Fer0x commented Sep 24, 2018

Summary

Flag --registry should have higher priority over publishConfig.registry like --access has higher priority over publishConfig.access. This makes usage of publish more explicit.

Test plan

// package.json
"publishConfig": {
  "registry": "https://my.registry/"
}
yarn test --registry http://my.another.registry/

@Fer0x
Copy link
Contributor Author

Fer0x commented Feb 26, 2019

@arcanis please include it in next version.

@Fer0x
Copy link
Contributor Author

Fer0x commented Jan 21, 2020

@arcanis any chance to merge it?

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

Successfully merging this pull request may close these issues.

None yet

2 participants