![]() Which added nvm the lines I previously had removed in my. Then started a new shell (so that nvm isn't loaded in this new shell) and ran curl -o- | bash zshrc to remove the lines related to nvm, which in my case were export NVM_DIR="$HOME/.nvm" ![]() I followed by running $ rm -rf "$NVM_DIR" I uninstalled and reinstalled nvm entirely to fix it. It wasn't possible to change node's version anymore. $ npm config set prefix $NVM_DIR/versions/node/v6.11.1Īfter running the recommended commands my nvm didn't work anymore, running nvm use would display the proper node version being used, but running node -v would show another. I followed answer but it didn't work out well. Nvm is not compatible with the npm config "prefix" option: currently set to "/home/john" Run `npm config delete prefix` or `nvm use -delete-prefix v0.10.44` to unset it. Nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local" ![]() Note that you will have to repeat the same procedure with every node version, the prefix is set back to (in my case) /usr/local after installation. When I tried npm config delete prefix or nvm use -delete-prefix before using npm -prefix="" set prefix "", I got only: I was able to set to prefix with the help of this post: I think it should be hard-coded on Linux, so that it's specified as /etc/npmrc at (RPM-) build time.I was looking for a solution for the nvm prefix problem a found this question(before finding the solution). ![]() npm shouldn't be using this lousy definition of its PREFIX. Unfortunately, it looks like npm picks its $/, though I am _not_ knowledgeable enough in this area, and there may be a very good reason for this.Ģ. Please, consider reopening (or should I create a new bug?).įedora 22, x86-64, npm-1.3. and nodejs-0.10.86_64.Ĭat: /usr/etc/npmrc: No such file or directory ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |