The full name of NUCM is NPM User Change Manager, an efficient and intuitive tool for managing NPM account switches. It provides developers with a straightforward way to easily switch and manage different NPM user accounts. Whether working on multiple projects, collaborating with others, or switching between different work environments, this tool helps users maintain a seamless NPM package management experience.
Document address:https://beezen.github.io/nucm/
$ npm install -g nucm # or yarn global add nucm
Usage: nucm [options] [command]
Options:
-v,--version show version
-h, --help display help for command
Commands:
ls [options] show account list
use [options] <name> switch account
add <name> <access-tokens> add account
del <name> remove account
localize|language <lang> use localized languages
update [options] updated version
save Save the current account
registry|nrm <cmd...> Registration source configuration
help [command] display help for command
$ nucm save
$ nucm add beezen abcdefXXXXXXXXmno2
Account added successfully
$ nucm ls
beezend -- abcdef......mno1
beezen --- abcdef......mno2
* beeze ---- abcdef......mno3
$ nucm use beezen
Switched to account beezen
We manage the Access Token released by NPM.
An access token is an alternative to using your username and password for authenticating to npm when using the API or the npm command-line interface (CLI). An access token is a hexadecimal string that you can use to authenticate, and which gives you the right to install and/or publish your modules.
Note: If you have logged in through npm login or npm adduser, you can preserve the access token of the current login account by executing the nucm save command.
During subsequent use, you can swiftly switch between accounts using the nucm use command, enabling quick switching of the associated Access Token. This allows seamless release of NPM packages with different account credentials.
If you want to learn more about the configuration of NPM login, you can refer to the .npmrc configuration instructions.
MIT