NVM is not compatible with the npm config "prefix" option warning (OS X)

Question

NVM is not compatible with the npm config "prefix" option warning (OS X)

peteringraham opened this issue 8 years ago · comments

Split off from #855 ; see that issue for a similar problem.

This is in OS X El Capitan, 10.11.6 . This error appears on starting a new shell:

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 v5.7.1 --silent` to unset it.

With the usual command in the .bashrc file:

export NVM_DIR="/Users/pingraham/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

Running either or both of the suggested fixes don't appear to do anything, though.

Note: I foolishly installed some node version globally while trying to fix this, and also foolishly upgraded npm once in an attempt to fix this, but ran into an entirely different npm bug ( npm/npm#13918 , if you're curious ) before giving up. On the other hand, NVM seems to sorta work anyway...? Maybe?

Here's some commands & their results:

node -v
v5.7.1

nvm use 5.7.1
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 v5.7.1` to unset it.

Running either or both of the suggested command doesn't change anything.

Oddly enough, the switch seems to work anyway... maybe...

nvm use 0.10
Now using node v0.10.33 (npm v1.4.28)

node -v
v0.10.33

nvm use 5.7.1
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 v5.7.1` to unset it.

node -v
v5.7.1

(I guess it happened regardless??)

Debugging info:

echo $PREFIX ; echo $NPM_CONFIG_PREFIX

(nothing, just empty lines)

nvm debug
nvm --version: v0.32.0
$SHELL: /bin/bash
$HOME: /Users/pingraham
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: system
which node: /usr/local/bin/node
which iojs: 
which npm: /usr/local/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules

(nvm debug, after switching)

nvm current: v0.10.33
which node: $NVM_DIR/v0.10.33/bin/node
which iojs: 
which npm: $NVM_DIR/v0.10.33/bin/npm
npm config get prefix: $NVM_DIR/v0.10.33
npm root -g: $NVM_DIR/v0.10.33/lib/node_modules

nvm ls
       v0.10.33  
         v5.7.1  
->       system  
default -> 5.7.1 (-> v5.7.1)
node -> stable (-> v5.7.1) (default)
stable -> 5.7 (-> v5.7.1) (default)
iojs -> N/A (default)
lts/* -> lts/argon (-> N/A)
lts/argon -> v4.5.0 (-> N/A)

No prefixes set in the environment, either:

$PREFIX: ''
$NPM_CONFIG_PREFIX: ''

It seems wrong to just ignore the error! Any ideas on what I could change? And is it a "Real" error, or just noise, since it seems that at least node -v acknowledges the switches anyway?

Jordan Harband · Answer 1 · Tue Sep 27 2016 01:43:29 GMT+0800 (China Standard Time)

(also per #855 (comment), you don't have any "prefix" in any .npmrc files, and per #855 (comment), you don't have any case-insensitive form of "prefix" in env)

I assume that nvm ls, after the nvm use, has the -> pointing at "v5.7.1"?

Do you have anything in ~/.bash_profile and/or ~/.bashrc that refers to PATH, nvm, or npm?

I'm seeing a few strange things here:

nvm use complains about the prefix, but you don't have any prefix overrides set anywhere
when nvm use complains about the prefix, the node version still changes (it should be running nvm deactivate after printing that error)

Peter Ingraham · Answer 2 · Tue Sep 27 2016 05:40:04 GMT+0800 (China Standard Time)

I don't believe so, as far as PATH /nvm / npm references of note. My ~/.bash_profile:

source ~/.bashrc

if [ -f ~/.git-completion.bash ]; then
  . ~/.git-completion.bash
fi

The source of the bashrc seems like it shouldn't really be necessary to me, but .bashrc doesn't run if I don't include it.

The only thing in .bashrc of potential interest is pretty bog-standard:

export NVM_DIR="/Users/pingraham/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

eval "$(grunt --completion=bash)"

For nvm ls: Not that one version. If I use 5.7.1, it points to "system" instead (which is hopefully harmless, since node -v indicates system IS 5.7.1 ). npm -v says it is 3.6.0. If I use some other version (e.g. v.0.10.36), then it points to that, yes (and npm -v gives 2.20 ).

(after terminal start, or nvm use 5.7.1)

nvm ls
       v0.10.33  
       v0.10.36  
         v5.7.1  
->       system  
default -> 5.7.1 (-> v5.7.1)
node -> stable (-> v5.7.1) (default)
stable -> 5.7 (-> v5.7.1) (default)
iojs -> N/A (default)
lts/* -> lts/argon (-> N/A)
lts/argon -> v4.5.0 (-> N/A)

Thanks for looking into this!

Jordan Harband · Answer 3 · Tue Sep 27 2016 07:15:23 GMT+0800 (China Standard Time)

@peteringraham hm, it's possible that v5.7.1 is corrupted? could you try nvm uninstall v5.7.1 && nvm install v5.7.1 and see if the issue is fixed?

Peter Ingraham · Answer 4 · Tue Sep 27 2016 23:27:29 GMT+0800 (China Standard Time)

Looks like it worked. I guess this was a side-effect of sudo npm install -g when trying to fix unrelated errors earlier.

nvm uninstall 5.7.1
file is not writable: $NVM_DIR/versions/node/v5.7.1/bin/grunt
Cannot uninstall, incorrect permissions on installation folder.
This is usually caused by running `npm install -g` as root. Run the following commands as root to fix the permissions and then try again.

  chown -R pingraham "$NVM_DIR/versions/node/v5.7.1"
  chmod -R u+w "$NVM_DIR/versions/node/v5.7.1"

After running those, uninstalling, and reinstalling, no error message, node -v returns 5.7.1.

I'll re-open if something surprising happens later, but I think this is mostly fixed.

Note that nvm ls now claims it's using "5.7.1" rather than "system", so maybe using the system version of node isn't really supported? OTOH, this might be too specific & weird a situation to bother having specific commentary on.

Thanks again for your help.

Elijah M. · Answer 5 · Thu Aug 31 2017 14:01:31 GMT+0800 (China Standard Time)

@ljharb Thanks! nvm uninstall v5.7.1 && nvm install v5.7.1 worked for me.

Andy Edwards · Answer 6 · Wed Dec 13 2017 03:35:37 GMT+0800 (China Standard Time)

None of the fixes here seem to have worked for me, and I get this error regardless of which version I'm trying to switch to.

However, if I merely run nvm use a second time, it succeeds. I wonder if that's why some of these fixes "worked" for other folks here? If I open a new terminal I get the error again the first time I run nvm use, and after that it's okay.

Jordan Harband · Answer 7 · Wed Dec 13 2017 04:18:45 GMT+0800 (China Standard Time)

@jedwards1211 is there any chance you have something in your shell profile files that modifies the PATH after nvm is sourced? If so, a second nvm use would correct the PATH.

Andy Edwards · Answer 8 · Wed Dec 13 2017 04:25:11 GMT+0800 (China Standard Time)

@ljharb why yes 😃 moving source nvm after all of that fixed my problem, thanks!
The offending line was pretty obvious in retrospect:

PATH="/usr/local/bin:/usr/local/opt/subversion/libexec:/opt/apache-maven-3.3.9/bin:$PATH"

Antony Jones · Answer 9 · Wed Jan 10 2018 00:25:07 GMT+0800 (China Standard Time)

Wow I'm tired of this issue - seems to affect me randomly on various machines and CI environments. 3 years old and still going strong.

Not sure why it's marked as fixed? Nothing is fixed... none of the above solutions seem to work for me.

MwumLi · Answer 10 · Wed Feb 28 2018 14:08:36 GMT+0800 (China Standard Time)

@antony you can try the ways:

comment out the code below in your shell file (such as ~/.zshrc):

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

log out your account and log in
uncommnet these code above and source shell file

r4bbit · Answer 11 · Mon Mar 05 2018 19:55:21 GMT+0800 (China Standard Time)

If you're using any other shell than bash, make sure to configure your tmux that way:

# set default shell to zsh
set -g default-command /bin/zsh
set -g default-shell /bin/zsh

This solved it for me.

akrois · Answer 12 · Wed Mar 14 2018 22:42:35 GMT+0800 (China Standard Time)

MWumLi's fix worked for me. Yes, this was highly annoying and time-consuming to fix. I'm happy to report the fix is quite simple.

MwumLi · Answer 13 · Thu Mar 15 2018 18:36:42 GMT+0800 (China Standard Time)

When I use tmux, the bug apear, so I view code, find the real reason is PATH overlap which result in Determine if the nvm path exists error

How to solve the bug?
There're three way:

simple, but you cann't set default: nvm unalias default
complex, modify function nvm_change_path:

nvm_change_path() {
  local NVM_NPM_PREFIX
  NVM_NPM_PREFIX="$(npm config --loglevel=warn get prefix)"
  # if there’s no initial path, just return the supplementary path
  if [ -z "${1-}" ]; then
    nvm_echo "${3-}${2-}"
  # if the initial path doesn’t contain an nvm path, prepend the supplementary
  # path
  elif ! (nvm_tree_contains_path "$NVM_DIR" "$NVM_NPM_PREFIX" >/dev/null 2>&1); then
    nvm_echo "${3-}${2-}:${1-}"
  # use sed to replace the existing nvm path with the supplementary path. This
  # preserves the order of the path.
  else
    nvm_echo "${1-}" | command sed \
      -e "s#${NVM_DIR}/[^/]*${2-}[^:]*#${3-}${2-}#g" \
      -e "s#${NVM_DIR}/versions/[^/]*/[^/]*${2-}[^:]*#${3-}${2-}#g"
  fi
}

Hope someone can make a PR, 👏

Prachi · Answer 14 · Thu Apr 26 2018 23:56:39 GMT+0800 (China Standard Time)

It is not fixed! i'm having the same problem for multiple versions of node. tried uninstalling and reinstalling as suggested in some of the comments above. But that did not fix it for me.

Yochem van Rosmalen · Answer 15 · Sat May 05 2018 00:49:54 GMT+0800 (China Standard Time)

nvm unalias default worked for me! Much appreciated @MwumLi 🍻

Ferdi · Answer 16 · Wed May 09 2018 00:24:51 GMT+0800 (China Standard Time)

The Fix
rm $(which npm) if and only if it was installed by a non-nvm node and is taking precedence over nvm's node.

You can check this by doing the following:

nvm deactivate
ls -la $(which npm)

If it points to something outside of $NVM_DIR it may be causing problems.

The explanation
I ran into this today ONLY when starting tmux.
I am using oh-my-zsh on a mac however I think the following may benefit anyone.

First, I uninstalled node from brew brew uninstall node
Then I debugged a ton and found that the npm being used was a leftover from my brew node installation.
npm was located at /usr/local/bin/npm but symlinked to /usr/local/lib/node_modules.
Because of this, the default prefix was takining over and set to /usr/local.

So I performed the following to ensure brew's node was gone:

sudo rm -rf  /usr/local/lib/node_modules
rm /usr/local/bin/npm
brew uninstall --force node
brew prune

No more errors YAY!

In hindsight, I believe all I really needed to do was either rm the npm symlink in /usr/local/bin and perhaps the npm install source at /usr/local/lib/node_modules/bin/npm (not sure of this path).

Dmitrii Kanatnikov · Answer 17 · Thu May 10 2018 15:43:22 GMT+0800 (China Standard Time)

@MwumLi nvm_change_path:2: command not found: npm

MwumLi · Answer 18 · Sat May 12 2018 17:06:32 GMT+0800 (China Standard Time)

@rifler Do you install npm? Your result show npm not be installed.

Dmitrii Kanatnikov · Answer 19 · Sat May 12 2018 22:01:51 GMT+0800 (China Standard Time)

globally not, only via nvm

MwumLi · Answer 20 · Tue May 15 2018 20:05:49 GMT+0800 (China Standard Time)

@rifler Here, first say sorry, my code has little bug.
npm config --loglevel=warn get prefix get current node path, but the above code not include the condition which npm has been not installed, so, you should add the judge: if npm not installed, this means node not be installed , you can use nvm_echo "${3-}${2-}:${1-}" directly.
I read nvm code a long time ago , so there may be some mistakes. 🤭

r1b · Answer 21 · Fri May 25 2018 22:32:37 GMT+0800 (China Standard Time)

@Strongbyte-FP This was exactly my problem - thank you!

David Daniel · Answer 22 · Sat Jun 09 2018 07:35:58 GMT+0800 (China Standard Time)

I was able to leave the system node on and simply remove the npm install that it came with (might not need the system node anyway so it's probably going out - it might be that something needed it - cannot remember....)

rm -rf /usr/local/lib/node_modules/npm

That was enough for me.

xwchris · Answer 23 · Wed Jul 11 2018 09:35:53 GMT+0800 (China Standard Time)

I tried all but still not work for me.
I use where node and found I have a node of global in /usr/local/bin/node.
then I use this to delete it

sudo rm -rf /usr/local/lib/node_modules
sudo rm /usr/local/bin/node
cd  /usr/local/bin && ls -l | grep "../lib/node_modules/" | awk '{print $9}'| xargs rm

and then, it work for me!!!

Dmitrii Kanatnikov · Answer 24 · Sat Jul 21 2018 03:52:33 GMT+0800 (China Standard Time)

I realised, that this behaviour connected with commitizen
when I simply run git commit -am "msg" - all hooks run fine
when I run git-cz - I get

nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/Users/rifler/.nvm/versions/node/v10.6.0"
Run `unset npm_config_prefix` to unset it.
husky > can't find npm in PATH, skipping precommit script in package.json
nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/Users/rifler/.nvm/versions/node/v10.6.0"

Matt Travi · Answer 25 · Sat Jul 21 2018 03:57:42 GMT+0800 (China Standard Time)

@rifler are you using husky along with commitizen, by chance?

the latest version of husky (and many previous versions) leverages nvm to run your tests in the version of node defined in your .nvmrc. the newest versions, that haven't hit latest yet, don't do this anymore (i think because it is assumed that if you are using nvm that you are already running the correct version through other means), so they avoid this problem.

try npm install husky@next -D if this does apply to you and see if it resolves this particular issue.

Dmitrii Kanatnikov · Answer 26 · Sat Jul 21 2018 04:01:24 GMT+0800 (China Standard Time)

@travi it helps, thank you!

Giedrius Rimkus · Answer 27 · Wed Oct 24 2018 16:59:57 GMT+0800 (China Standard Time)

nvm unalias default worked for me! Much appreciated @MwumLi 🍻

Thanks. This one helped for me.

Luqman Olushi O. · Answer 28 · Sun Nov 11 2018 10:16:05 GMT+0800 (China Standard Time)

nvm unalias default

Thanks. Worked for me.

Ramananda Panda · Answer 29 · Tue Nov 13 2018 19:54:49 GMT+0800 (China Standard Time)

I just close the terminal by right clicking the icon below and clicking on force quit and reopened it. This worked for me.

zimingsong · Answer 30 · Thu Mar 21 2019 20:45:30 GMT+0800 (China Standard Time)

@antony you can try the ways:

comment out the code below in your shell file (such as ~/.zshrc):
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
log out your account and log in

uncommnet these code above and source shell file

This worked for me! Thanks!

Cody Swartz · Answer 31 · Fri Mar 22 2019 08:51:59 GMT+0800 (China Standard Time)

Not sure what installed a global npm for me, but I ran this to have npm uninstall itself

Note: I had to run this twice.

# Run until which npm returns: npm not found
npm un -g npm
which npm

Afterwards I uninstalled my current nvm node version I was on, and then reinstalled it to get a standard npm back and running.

CURRENT_NODE_VERSION="$(nvm version)"
nvm use vSOMETHING_ELSE
nvm uninstall $CURRENT_NODE_VERSION
nvm install $CURRENT_NODE_VERSION

Hope this helps someone...

Jordan Harband · Answer 32 · Fri Mar 22 2019 08:58:03 GMT+0800 (China Standard Time)

@ctsstc global npm comes with node, and you should never uninstall it - the only cure is reinstalling node to get it back.

Cody Swartz · Answer 33 · Fri Mar 22 2019 09:25:12 GMT+0800 (China Standard Time)

@ljharb if you're using nvm it should be located under your nvm versions like:

/Users/codyswartz/.nvm/versions/node/v11.12.0/bin/npm

Not something like the following that mine was pointed at:

/usr/local/bin/npm

Yet when I ran which node it was pointing at nvm, so that's why I was confused where the rouge global nvm came from. It might have been from some ruby gem I installed recently. I treat node installs Ephemerally so reinstalling isn't much concern for me.

Greck Pastor · Answer 34 · Thu Apr 04 2019 23:18:59 GMT+0800 (China Standard Time)

nvm unalias default worked for me! Much appreciated @MwumLi 🍻
this is the solution :)

Jordan Harband · Answer 35 · Fri Apr 05 2019 00:40:52 GMT+0800 (China Standard Time)

Doing that will mean your shell starts out without any node version available, please note.

Brady Dowling · Answer 36 · Wed May 01 2019 22:11:42 GMT+0800 (China Standard Time)

@ljharb I'm thinking the same thing. Removing the default alias fixed this but shouldn't there be another way around this?

Update: As a workaround, I removed the default alias and then added the following to my .bashrc file.

nvm use --delete-prefix v8.16.0

That did the trick but then I decided to give the chosen answer here one more shot (which I'm sure I had done in the past) and it actually worked for me.

$ npm config delete prefix
$ npm config set prefix $NVM_DIR/versions/node/v8.16.0 # Where v8.16.0 is the version you want

If this doesn't work for you then try unsetting default and then adding the --delete-prefix line I included above in your .bashrc or .zshrc file.

Brandon Pereira · Answer 37 · Thu Jun 27 2019 06:50:36 GMT+0800 (China Standard Time)

I fixed this by deleting a ~/.huskyrc file. Not sure how it got there, but I tested my hooks after deleting it and they still work.

Travis Delly · Answer 38 · Thu Jul 04 2019 03:05:43 GMT+0800 (China Standard Time)

Pretty simple fix

Navigate to your .nvm folder remove all npm version, since you can just reinstall with nvm easily then run unset npm_prefix_config, then install some arbitrary npm version using nvm, then run nvm use {version you installed}

Boom npm is usable again.

EDIT:

My Mistake the final command you must run is

ln -s $(which node) /usr/local/bin/node

which should put the current node being used in the path.

Morteza Ziyaeimehr · Answer 39 · Sun Jul 14 2019 23:07:08 GMT+0800 (China Standard Time)

In my case, I just uninstalled nodejs installed by system (sudo apt uninstall nodejs), removed ~/.nvm folder, cleaned up .bashrc and .zshrc from nvm related commands, then installed nvm again.

Radu Micu · Answer 40 · Thu Aug 22 2019 18:05:23 GMT+0800 (China Standard Time)

Fro those coming here and you are using a Mac, my issue was that my user folder had upper case letters in it, but my profile folder setting under users pointed to the all lower case path version of it. Once I logged in from another account renamed to have all lower case all worked just fine.

Derek Delaney · Answer 41 · Fri Aug 23 2019 00:04:42 GMT+0800 (China Standard Time)

I found that @bradydowling's fix worked for me. I recently installed yvm with brew and I guess it needed node as a dependency. Therefore I had a system node that couldn't handle the default prefix. Removing it with brew removed the error.

Jovan Gerodetti · Answer 42 · Mon Sep 16 2019 21:05:30 GMT+0800 (China Standard Time)

I go this error because my $HOME contains a slash at the end on macOS 10.14 so my NVM_PATH looked like this /Users/username//.nvm.
Changing the NVM_PATH to export NVM_DIR="$HOME.nvm" solved the issue.

EDIT: changing the home location in the macOS user settings is actually the better solution.

Jon Lam · Answer 43 · Wed Nov 20 2019 01:07:43 GMT+0800 (China Standard Time)

@TitanNano's fix worked fo rme too. Mine was set to export NVM_DIR=~/.nvm which i guess didn't have a good reference back to the real home

James Dixon · Answer 44 · Mon Dec 30 2019 05:55:47 GMT+0800 (China Standard Time)

Doing that will mean your shell starts out without any node version available, please note.

Exactly. nvm unalias default isn't a good solution

Ivan Zinkevich · Answer 45 · Mon Jan 06 2020 22:26:58 GMT+0800 (China Standard Time)

Doing that will mean your shell starts out without any node version available, please note.

Exactly. nvm unalias default isn't a good solution

Still a good solution :)

GradedJestRisk · Answer 46 · Sat Feb 22 2020 18:38:22 GMT+0800 (China Standard Time)

I came against the same problem.
I reinstalled nvm, using zsh custom plugin, then everything went fine 😄
Here, section "As an Oh My ZSH! custom plugin"

Dick Wyn Yong · Answer 47 · Wed Apr 15 2020 02:33:24 GMT+0800 (China Standard Time)

I fixed it by seeing the prefix to the current version of node that I was using
npm config set prefix $NVM_DIR/versions/node/12.16.2

Jordan Harband · Answer 48 · Wed Apr 15 2020 02:46:02 GMT+0800 (China Standard Time)

@dickwyn that's not a good fix; you shouldn't have a prefix set at all - doing that will break as soon as you're not using v12.16.2.

Dick Wyn Yong · Answer 49 · Wed Apr 15 2020 02:51:48 GMT+0800 (China Standard Time)

@ljharb so, should I remove the prefix with npm config delete prefix?

Jordan Harband · Answer 50 · Wed Apr 15 2020 03:01:04 GMT+0800 (China Standard Time)

@dickwyn you should ensure that ~/.npmrc, and your env, all have no mention of prefix (in the env, in any capitalization)

Pavan Chilukuri · Answer 51 · Sat Apr 18 2020 09:01:14 GMT+0800 (China Standard Time)

Do you have anything in ~/.bash_profile and/or ~/.bashrc that refers to PATH, nvm, or npm?

I had something like source ~/.nvm/nvm.sh in my ~/.zshrc. Once I removed it, i don't see the error message.

karlmacklin · Answer 52 · Tue May 05 2020 15:10:55 GMT+0800 (China Standard Time)

nvm unalias default worked for me as well, thanks.

I had this problem not when launching Ubuntu (in my WSL 1 env in Win10), but when opening tmux within it. Super annoying, those error messages should be removed since doing the fixes in them didn't help at all.

Haja Rasoahaingo · Answer 53 · Fri Jun 19 2020 06:42:52 GMT+0800 (China Standard Time)

Just run into this issue, and here's what I did to fix it:

remove node: brew uninstall node
install desired version: nvm install 'lts/*'
set the default version: nvm alias default 'lts/*'
delete npm prefix: npm config delete prefix
set prefix to the node version used with nvm: npm config set prefix $NVM_DIR/versions/node/v12.18.1

Jordan Harband · Answer 54 · Fri Jun 19 2020 06:59:33 GMT+0800 (China Standard Time)

Setting the prefix like that is both unnecessary and will prevent nvm from being able to switch versions.

Haja Rasoahaingo · Answer 55 · Fri Jun 19 2020 07:31:40 GMT+0800 (China Standard Time)

@ljharb I had no issue switching from 12.x to 14.x 😉

Jordan Harband · Answer 56 · Fri Jun 19 2020 12:34:17 GMT+0800 (China Standard Time)

@hrasoa if in node 14, npm root -g points to node 12's npm, you will have issues. Global modules must not be shared across node versions.

Michael Hunter · Answer 57 · Tue Jul 14 2020 08:27:30 GMT+0800 (China Standard Time)

The route that got me to this error was mixing installations of node based packages using nvm and brew. This can get a bit painful as installing the heroku tools or yarn will install their own version of node. I was able to resolve my issues by only ever using nvm. Big YMMV.

Torben Larsen · Answer 58 · Tue Nov 10 2020 16:00:52 GMT+0800 (China Standard Time)

I had the same issue as @radum - renaming my user folder to not include uppercase letters fixed it.
That really shouldn't be necessary IMO.

Jordan Harband · Answer 59 · Wed Nov 11 2020 10:45:10 GMT+0800 (China Standard Time)

@tflx i agree - but did the casing of whoami and echo $HOME match? if not, fix that, as that's the issue.

Sammy Baraka · Answer 60 · Fri Nov 20 2020 08:15:53 GMT+0800 (China Standard Time)

none of these work for my raspberry pi 3 running raspberry OS

Jordan Harband · Answer 61 · Fri Nov 20 2020 12:52:35 GMT+0800 (China Standard Time)

@sbaraka then please file a new issue and file out the entire issue template. Thanks!

Patrick · Answer 62 · Fri Jun 18 2021 18:18:09 GMT+0800 (China Standard Time)

Just setting the prefix to the nvm version I use helped: npm config set prefix $NVM_DIR/versions/node/v14.15.3 Replace the version with yours of course 👍🏻

Jordan Harband · Answer 63 · Fri Jun 18 2021 23:14:06 GMT+0800 (China Standard Time)

@mklb definitelt don’t do that; that will break the moment you try to change node versions. Prefix should never be set at all.

Patrick · Answer 64 · Sat Jun 19 2021 02:38:45 GMT+0800 (China Standard Time)

Good point @ljharb - the better fix was deleting the version entry in ${HOME}/.npmrc. No idea how it got there..

Lucas Rueda · Answer 65 · Wed Aug 18 2021 03:51:17 GMT+0800 (China Standard Time)

In my case I had:

nvm as oh-my-zsh plugin
NVM_LAZY=1
NVM_AUTOLOAD=1

I had to remove the NVM_LAZY variable from .zshrc and everything worked

Cris · Answer 66 · Mon Nov 01 2021 19:49:24 GMT+0800 (China Standard Time)

If I want to run nvm in somewhere inside an npm script (or in the subprocess tree of one), then I do:

#!/bin/bash

unset npm_config_prefix

source $HOME/.nvm/nvm.sh
. $HOME/.profile

version=v14.15.3 

nvm install $version
nvm use $version

# rest of script that uses node version $version