Skip to content

Instantly share code, notes, and snippets.

@ivermac

ivermac/nvm-compatiblity-issue.md

Last active March 7, 2018 09:41
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ivermac/25057d19e61119b1bc282195e1f3c31b to your computer and use it in GitHub Desktop.
Save ivermac/25057d19e61119b1bc282195e1f3c31b to your computer and use it in GitHub Desktop.
Download ZIP
nvm compatible issue
Raw
nvm-compatiblity-issue.md

I noticed the following warning being triggered when launching the terminal in my Visual Studio app a couple of times but I had ignored it:

➜ 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 v8.0.0 --silent` to unset it.

I got the exact same warning when launching tmux locally and that caught my attention. I use nvm locally to manage node versions so initially I thought that was the problem. A quick search on google and I found out that a couple of people had experienced the same problem. I found my solution here in a github issue. In my case, installing yarn via brew had resulted to a node being installed. When I ran which node, it was pointing to /usr/local/bin/node. I brew uninstalled both yarn and node and that seems to have fixed the problem on both tmux and the terminal in Visual Studio Code. When i'll need to use yarn, i'll figure out how it will play with the node version mananged by nvm 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment