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
Naming conflicts #33
Comments
Anyone knows a better way to solve this? Frankly, any cli names could potentially conflict with others. I would like to have something like "optional binary" for npm and let users select which cli they want or not. |
After search solutions for this problem, there is no good answer. |
Is it possible to take a page from python virtual env and enter a proprietary env environment |
I can't install 52 verbose argv "/Users/edz/.nvm/versions/node/v16.13.0/bin/node" "/Users/edz/.nvm/versions/node/v16.13.0/bin/npm" "i" "-g" "@antfu/ni"
53 verbose node v16.13.0
54 verbose npm v8.1.0
55 error code EEXIST
56 error path /Users/edz/.nvm/versions/node/v16.13.0/bin/nrm
57 error EEXIST: file already exists
58 error File exists: /Users/edz/.nvm/versions/node/v16.13.0/bin/nrm
59 error Remove the existing file and try again, or run npm
60 error with --force to overwrite files recklessly.
61 verbose exit 1 |
|
for me, mv /usr/local/bin/nrm /usr/local/bin/nrt
npm i -g @antfu/ni |
Something somewhat related is the command Would you consider adding an alias to the I do understand it's impossible to avoid collission with ALL the CLI tools out there, but NX is a pretty big one and might be worth considering 🤔 |
|
After install
ni
globally, I found nrm instruction is substituted byni
feature.Usually, I use nrm as managing npm registries tools.
So, can we rename nrm to other name? From the download size of nrm, it was commonly used.
The text was updated successfully, but these errors were encountered: