nvm current returns system instead of version number, suspect nvm use not working #2686

zigotica · 2021-12-15T22:09:39Z

problem description

nvm current returns system instead of version number (i.e. v16.13.1). I need the version number not an alias, I suspect nvm use vX.Y.Z is not working.

Operating system and version:

macOS 12.1 21C52 arm64

`nvm debug` output:

nvm --version: v0.39.0
$TERM_PROGRAM: tmux
$SHELL: /opt/homebrew/bin/bash
$SHLVL: 2
whoami: 'sergi'
${HOME}: /Users/sergi
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: /opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:${NVM_DIR}/versions/node/v16.13.0/bin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/kitty.app/Contents/MacOS:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:${HOME}/bin:${HOME}/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.1.12(1)-release (aarch64-apple-darwin21.1.0)'
uname -a: 'Darwin 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T6000 arm64'
checksum binary: 'sha256sum'
OS version: macOS 12.1 21C52
curl: /usr/bin/curl, curl 7.77.0 (x86_64-apple-darwin21.0) libcurl/7.77.0 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.42.0
wget: /opt/homebrew/bin/wget, GNU Wget 1.21.2 built on darwin21.1.0.
sed: /opt/homebrew/opt/gnu-sed/libexec/gnubin/sed
cut: /usr/bin/cut
basename: /usr/bin/basename
rm: /bin/rm (rm -i)
mkdir: /bin/mkdir
xargs: /opt/homebrew/opt/findutils/libexec/gnubin/xargs
git: /opt/homebrew/bin/git, git version 2.34.1
grep: /opt/homebrew/opt/grep/libexec/gnubin/grep, grep (GNU grep) 3.7
awk: /opt/homebrew/bin/awk, awk version 20180827
nvm current: system
which node: /opt/homebrew/bin/node
which iojs:
which npm: /opt/homebrew/bin/npm
npm config get prefix: /opt/homebrew
npm root -g: /opt/homebrew/lib/node_modules

`nvm ls` output:

       v12.14.1
       v16.13.0
->       system
default -> v16.13.0
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v16.13.0) (default)
stable -> 16.13 (-> v16.13.0) (default)
lts/* -> lts/gallium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.7 (-> N/A)
lts/fermium -> v14.18.2 (-> N/A)
lts/gallium -> v16.13.1 (-> N/A)

How did you install `nvm`?

Homebrew

What steps did you perform?

brew install nvm

What happened?

Worked

Is there anything in any of your profile files that modifies the `PATH`?

Yes, PATH is listed in the debug output above

The text was updated successfully, but these errors were encountered:

ljharb · 2021-12-15T22:39:28Z

nvm is explicitly unsupported when installed via homebrew; what happens if you try installing nvm with the install script?

In this case, it's probably that your homebrew-managed PATH isn't correctly allowing nvm's path to take precedence over /opt/homebrew/bin/, and i'm not sure how to fix that while still using homebrew for nvm (or node, for that matter)

zigotica · 2021-12-16T08:53:32Z

OHMY, what an embarrassment, I cannot read. Yes, uninstalling brew nvm and running the official install from curl did the trick. Please accept my apologies, and thank you.

zigotica · 2021-12-16T15:20:24Z

Sorry, there must be somethign else. I unsinstalled the brew version, installed nvm through curl. I still cannot change versions, current appears to be "system"

$ nvm install 16.0.0
Downloading and installing node v16.0.0...
Downloading https://nodejs.org/dist/v16.0.0/node-v16.0.0-darwin-arm64.tar.xz...
############################################################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v16.0.0 (npm v8.1.4)

$ nvm use 16.0.0
Now using node v16.0.0 (npm v8.1.4)

$ nvm alias default 16.0.0
default -> 16.0.0 (-> v16.0.0)

$ nvm use default
Now using node v16.0.0 (npm v8.1.4)

$ nvm ls
        v16.0.0
       v16.10.0
       v16.13.0
->       system
default -> 16.0.0 (-> v16.0.0)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v16.13.0) (default)
stable -> 16.13 (-> v16.13.0) (default)
lts/* -> lts/gallium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.7 (-> N/A)
lts/fermium -> v14.18.2 (-> N/A)
lts/gallium -> v16.13.1 (-> N/A)


$ nvm current
system

Again my config:

$ nvm --version
0.39.0

$ which node
/opt/homebrew/bin/node

$ which npm
/opt/homebrew/bin/npm

$ npm config get prefix
/opt/homebrew

$ npm root -g
/opt/homebrew/lib/node_modules

I honestly dont know where more to look at. Yes, I restarted terminal, and even the computer.

zigotica · 2021-12-16T15:52:41Z

I am suspecting nvm (or some node versions installed through it) will not work in M1 macs. And I am not willing to use Rosetta. A solution I found is bypassing nvm altogether, and install a specific version of node through brew, but then I am obviously missing the whole point of nvm (no versions are possible, other that installing/uninstalling node every time I change project).

ljharb · 2021-12-16T16:18:37Z

nvm works fine on M1 macs; but node itself doesn’t support m1 on less than v16 except with Rosetta.

ljharb · 2021-12-16T16:19:06Z

It’s possibly 16.0.0 doesn’t support it; but 16 latest certainly does. There’s a whole section in nvm’s readme about it.

zigotica · 2021-12-16T16:25:45Z

It’s possibly 16.0.0 doesn’t support it; but 16 latest certainly does. There’s a whole section in nvm’s readme about it.

Yeah, but same happens for v16.13.1, I still get the system response as if nvm is not used at all, which is driving me nuts.

ljharb · 2021-12-16T16:32:38Z

In that case it’s likely a PATH issue. Make sure sourcing nvm is the last thing in your profile file; or at least, that it happens after the last thing that prepends to the path.

zigotica · 2021-12-16T16:49:17Z

hold on, my problem is only inside tmux session! if I try nvm on a regular kitty tab it just works. inside tmux it does not... will investigate.

zigotica · 2021-12-16T16:51:31Z

the super weird thing about it is that inside AND outside tmux,

$ node -p process.arch
arm64

ljharb · 2021-12-16T17:07:09Z

What’s the PATH diff between inside and outside?

zigotica · 2021-12-16T17:12:55Z

OUTSIDE TMUX:

$ echo $PATH
/Users/sergi/.nvm/versions/node/v16.0.0/bin:/opt/homebrew/opt/node@17/bin:/opt/homebrew/opt/node@16/bin:/opt/homebrew/opt/node@14/bin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/kitty.app/Contents/MacOS:/Users/sergi/bin:/Users/sergi/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin

$ which npm
/Users/sergi/.nvm/versions/node/v16.0.0/bin/npm

$ node -v
v16.13.1

INSIDE TMUX:

$ echo $PATH
/opt/homebrew/opt/node@17/bin:/opt/homebrew/opt/node@16/bin:/opt/homebrew/opt/node@14/bin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/sergi/.nvm/versions/node/v16.0.0/bin:/opt/homebrew/opt/node@17/bin:/opt/homebrew/opt/node@16/bin:/opt/homebrew/opt/node@14/bin:/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/findutils/libexec/gnubin:/opt/homebrew/opt/grep/libexec/gnubin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/kitty.app/Contents/MacOS:/Users/sergi/bin:/Users/sergi/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin:/Users/sergi/bin:/Users/sergi/.config/bin:/usr/local/bin:/usr/local/sbin:usr/bin:/usr/sbin

$ which npm
/opt/homebrew/opt/node@16/bin/npm

$ node -v
v17.2.0

Going to look at those PATH changes as well. Thanks for all the help.

ljharb · 2021-12-16T17:20:38Z

That strongly implies that whatever profile file tmux sources (that your regular shell doesn't) is doing more PATH stuff with homebrew's node after nvm is sourced.

(node shouldn't ever be installed with homebrew regardless, but it shouldn't interfere with nvm at all)

zigotica · 2021-12-16T17:24:19Z

Yes, it's currently a mess. Most likely still artifacts from previous brew installs, since I was convinced brew was a viable option. I will try to remove all traces of nvm, npm, node, ... and reinstall nvm from curl/git again, to see if that helps. Thank you again.

ljharb · 2021-12-16T17:41:37Z

I'll close this for now, but will immediately reopen it if there's something actionable for nvm. Happy to continue discussing regardless.

zigotica · 2021-12-16T18:56:07Z

I can confirm this is now working in/outside of tmux. I did:

uninstall nvm, node, yarn
install nvm via git
add to path
install node via nvm
install yarn via brew

thank you again

zigotica · 2022-01-11T13:55:27Z

OK, sorry to reopen this issue. I had this all solved, but after installing another brew formula (that has node as a dependency), I am back to original problem. Inside tmux, node version is the one of the node dependency installed by that formula, no matter if I previously had installed nvm using git.

Not sure how to avoid this (besides uninstalling every formula that might have node as a dependency, which is bummer)

thank you

zigotica · 2022-01-11T15:25:05Z

OK, found this solution, but implies having to manually add each of node versions installed via nvm to the PATH, which is also a bummer.

ljharb · 2022-01-11T15:31:16Z

Yeah that sucks a lot. I think a better solution is rearranging your profile file so that homebrew’s path ends up after nvm’s - iow, make sure nvm’s lines are last

ljharb · 2022-01-11T16:07:47Z

Your PATH in nvm debug in the OP has /opt/homebrew/bin near the front. I think moving the homebrew paths to the end - or moving the nvm paths to the front - would do it.

zigotica · 2022-01-11T16:17:26Z

I fixed the loop, I don't need to export each path, just prepend it.

Your PATH in nvm debug in the OP has /opt/homebrew/bin near the front. I think moving the homebrew paths to the end - or moving the nvm paths to the front - would do it.

No, really, my brew file is sourced before my nvm file, and brew's node version. Don't ask me why. The only solution for me was to force the loop above.

zigotica · 2022-01-11T16:22:31Z

The reason why brew wins, is the way it creates the EXPORTs and PATH (the recommended way of doing so):

eval $(/opt/homebrew/bin/brew shellenv)

ljharb · 2022-01-11T16:38:10Z

does that eval happen before or after the nvm lines?

zigotica · 2022-01-11T16:39:04Z

does that eval happen before or after the nvm lines?

before

ljharb · 2022-01-11T16:40:01Z

ok, then i don't understand why nvm isn't able to force its stuff to go in the front of the PATH. Do you have a default set? nvm alias default node?

zigotica · 2022-01-11T16:44:46Z

ok, then i don't understand why nvm isn't able to force its stuff to go in the front of the PATH.

yeah, same here :)

Do you have a default set? nvm alias default node?

Yes, 16. But it doesn't matter, brew version (17) wins.

To be clear, it is working now, but it's a bit annoying to trace and discover. Just posted here so it can be tracked, for other people. Thank you again.

brendabispo · 2023-02-14T12:53:01Z

Try using:

arch -x86_64 zsh

Then try to install and run the nvm version you want. This will change the processor architecture to emulate old Intel chips.

reference

zigotica closed this as completed Dec 16, 2021

ljharb added installing nvm Problems installing nvm itself non-issue / invalid This isn't relevant to nvm, or turned out to be something unrelated. labels Dec 16, 2021

zigotica reopened this Dec 16, 2021

ljharb closed this as completed Dec 16, 2021

This comment was marked as outdated.

Sign in to view

james-prado mentioned this issue Jan 24, 2023

[Feature]: Prefer user installed node version when available. Shopify/cli#1202

Closed

This comment was marked as resolved.

Sign in to view

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

nvm current returns system instead of version number, suspect nvm use not working #2686

nvm current returns system instead of version number, suspect nvm use not working #2686

zigotica commented Dec 15, 2021

ljharb commented Dec 15, 2021

zigotica commented Dec 16, 2021

zigotica commented Dec 16, 2021 •

edited

Loading

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021 •

edited

Loading

zigotica commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022 •

edited

Loading

This comment was marked as outdated.

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

brendabispo commented Feb 14, 2023

This comment was marked as resolved.

nvm current returns system instead of version number, suspect nvm use not working #2686

nvm current returns system instead of version number, suspect nvm use not working #2686

Comments

zigotica commented Dec 15, 2021

problem description

Operating system and version:

nvm debug output:

nvm ls output:

How did you install nvm?

What steps did you perform?

What happened?

Is there anything in any of your profile files that modifies the PATH?

ljharb commented Dec 15, 2021

zigotica commented Dec 16, 2021

zigotica commented Dec 16, 2021 • edited Loading

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021

ljharb commented Dec 16, 2021

zigotica commented Dec 16, 2021 • edited Loading

zigotica commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022 • edited Loading

This comment was marked as outdated.

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

ljharb commented Jan 11, 2022

zigotica commented Jan 11, 2022

brendabispo commented Feb 14, 2023

This comment was marked as resolved.

`nvm debug` output:

`nvm ls` output:

How did you install `nvm`?

Is there anything in any of your profile files that modifies the `PATH`?

zigotica commented Dec 16, 2021 •

edited

Loading

zigotica commented Dec 16, 2021 •

edited

Loading

ljharb commented Jan 11, 2022 •

edited

Loading