Uninstall doesn't discuss restoring `npm set prefix %NODIST_PREFIX%\bin`
See original GitHub issueIs the correct uninstall procedure to npm config delete prefix
? If so, I can PR this into place.
Issue Analytics
- State:
- Created 9 years ago
- Comments:12
Top Results From Across the Web
nvm is not compatible with the npm config "prefix" option
nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local" Run "npm config delete prefix" or "nvm use --delete-prefix...
Read more >npm-prefix - npm Docs
Note: This command is unaware of workspaces. Description. Print the local prefix to standard output. This is the closest parent directory to contain...
Read more >Uninstalling packages and dependencies - npm Docs
To remove a package from your node_modules directory, on the command line, use the uninstall command. Include the scope if the package is...
Read more >npm-uninstall
This uninstalls a package, completely removing everything npm installed on its behalf. It also removes the package from the dependencies , devDependencies ...
Read more >removal - npm Docs
That will remove npm, but leave behind anything you've installed. ... node with a different --prefix , or installed npm with a different...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Check the
.npmrc
file in your windows user home directory, e.g.C:\Users\your-name-here\.npmrc
I actually think nodist is good, but nvm is also a great choice; there is a new package available for Windows that is not official, but works fine. I had this issue and saw that @robrich and @marcelklehr conclude on the same answer. Thanks to both of you. This worked for me! Using node 6.10.3 and npm 3.10.10