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

[Feature] Check npm login and registry before publishing #55

Closed
jamiebuilds opened this issue Feb 13, 2016 · 4 comments · Fixed by JetBrains/ring-ui#355
Closed

[Feature] Check npm login and registry before publishing #55

jamiebuilds opened this issue Feb 13, 2016 · 4 comments · Fixed by JetBrains/ring-ui#355

Comments

@jamiebuilds
Copy link
Contributor

@jamiebuilds jamiebuilds commented Feb 13, 2016

If you aren't logged in to npm, lerna should stop and ask you to login. It would be good if it logged you back out afterwards.

@sebmck
Copy link
Contributor

@sebmck sebmck commented Feb 13, 2016

If you're doing this for security then it's pointless.

@jamiebuilds
Copy link
Contributor Author

@jamiebuilds jamiebuilds commented Feb 13, 2016

I have to switch between npm profiles for different (public and private) registries

@jamiebuilds
Copy link
Contributor Author

@jamiebuilds jamiebuilds commented Feb 20, 2016

I'm going to just do a check at the beginning to make sure that you're logged in to the right registry.

$ npm whoami
$ npm config get registry

Logging in is overkill, but I think the more checks we can do at the beginning is good.

@jamiebuilds jamiebuilds changed the title npm login on publish Check npm login and registry before publishing Feb 20, 2016
@jamiebuilds jamiebuilds changed the title Check npm login and registry before publishing [Feature] Check npm login and registry before publishing Nov 16, 2016
@doug-wade doug-wade mentioned this issue Jan 5, 2017
@lock
Copy link

@lock lock bot commented Dec 27, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.