When logged into a registry that supports token-based authentication, tell the
server to end this tokens session. This will invalidate the token everywhere
youre using it, not just for the current environment.
When logged into a legacy registry that uses username and password authentication, this will
clear the credentials in your user configuration. In this case, it will only affect
the current environment.
If --scope is provided, this will find the credentials for the registry
connected to that scope, if set.
If specified, the user and login credentials given will be associated
with the specified scope. See npm help 7 npm-scope. You can use both at the same time,
npm adduser --registry=http://myregistry.example.com --scope=@myco
This will set a registry for the given scope and login or create a user for
that registry at the same time.