No documentation for "npm login"? #16487
Comments
|
Oh I see, thanks. I didn't look at that command because I didn't want to "add a new user". -- By letting "npm login" behave identical to "npm adduser", you essentially assume that they also have the exact same meaning. Isn't that a little problematic? What happens if I accidentally mistype my login/name? |
Ha, I almost expected a "Now that won't happen." kind of answer. Closing this issue, because the missing documentation turned out to be no mishap. -- IMHO, I'd even deprecate/remove the adduser command because account creation should be done by signing up directly to a registry. Also, if the maintainers of a private registry wanted to control who is publishing, they would have to partially disable that command by returning an error if the username doesn't exist. And I wouldn't add a 'delete user' command as mentioned by othiym23 in 8337. This would be asking for abuse. A user should have to directly log into a registry and use the account settings to mark his/her account for deletion. |
@rehieri It took me 10 or so minutes of googling to finally come across this thread to understand where login is documented. It being an alias for something else isn't a good reason not to document it - docs are for people who don't know that! Other doc on the site, such as https://docs.npmjs.com/private-modules/intro , use login, which is why I needed to look it up in the first place. It's fine if the doc is just a "See adduser" link. |
markdown files
documentation on npmjs.com
supporting information:
npm -v
prints: "4.2.0"node -v
prints: "v7.9.0"npm config get registry
prints: "https://registry.npmjs.org/"The text was updated successfully, but these errors were encountered: