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
publish using private registry argument #515
Comments
This was referenced Jan 30, 2017
Closed
You can do |
$ lerna publish --registry https://my-private-registry will be in the next release |
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I read many discussions about the possibility to publish to a private registry but is there a way to specify a private registry as an argument in the publish command ?
Using npm we can do
npm publish --registry http://my-private-registry
I can use the publishConfig configuration in each package.json but it's a duplication which is something that I want to avoid by using lerna ;-)
Do you think it's a good idea to have :
lerna publish --registry=http://my-private-registry
?The text was updated successfully, but these errors were encountered: