not able to install node 14 with nvm about nvm HOT 17 OPEN

If you have installed nvm using homebrew, then remove it

brew uninstall nvm

also

rm -rf $NVM_DIR

then install nvm 0.39.1 using the script and then install nvm install 14, it works. I had the same issue and managed to fix that using this version.

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

from nvm.

Where's the nvm debug output? The issue template is there for a reason, please fill it out in its entirety.

from nvm.

@raylancordeiro please provide everything the issue template asks for

from nvm.

@ljharb if you pay attention, @Vishnu94833 already shared the npm debug logs at the opening of the issue. Do you need more information?

from nvm.

@lucastorress if you pay attention, you’ll notice that those were edited in after i asked, and then the OP didn’t comment to notify me that it was there.

We have a code of conduct and that kind of hostile response won’t be tolerated.

from nvm.

@ljharb Don't get me wrong, I also found your response hostile at first, but the idea here is to understand and help.

The problem here on my machine is the same as reported by @Vishnu94833, the same version and the same operating system. This only happens in NodeJS version 14, with command nvm install 14.

I took a look at another issue, which indicates downgrading the version to 0.39.1, as 0.39.7 has this error.

Temporary solution found here: #3148 (comment)

from nvm.

It's not really an option; the python version required to build node is determined by node, and that's the only way to get it to work.

from nvm.

Worked flawlessly with v0.39.1 - I've had this same issue with a few other versions too, I guess I'll keep using 0.39.1 for a good while in the future while I still need node v14

from nvm.

You should provide the checksum in the index.tab file :-) then there won't be a warning.

from nvm.

I have the same problem, can you help?

from nvm.

What the error message shows is that it's requiring an older version of python than you have on your system. I have no idea why downgrading nvm would have any impact on that.

from nvm.

@ljharb , Thanks for the suggestion. but I want the latest version of Python as another dependency for Kubectl. Downgrading to an older version is clearly mentioned in the logs that I can see. I just wanted to know if there's a fix for my problem.

I forgot to mention you once I edited the template. I thought you'd be notified.

Thanks!

from nvm.

Lots of things won't work properly if you're on anything but the latest, so 0.39.1 isn't a great choice. Be on 0.39.7, and provide the info requested in the issue template, so I can fix it. I don't know what would be different in those versions that would make node 14 uninstallable, and I can install node 14 just fine on latest nvm.

from nvm.

... I want the latest version of Python as another dependency for Kubectl. Downgrading to an older version is clearly mentioned in the logs that I can see. I just wanted to know if there's a fix for my problem.

What if you run brew unlink first to restore the default python from macOS, then install node 14, and at last brew link latest python again?

brew link [email protected], puts 'python3.10' in your path but it doesn't make python3 reference the 3.10 version. I saw a thread from one of the homebrew developers who said they support alternate python versions with e.g.:

export PATH="$(/opt/homebrew/bin/brew --prefix [email protected])/libexec/bin:$PATH"

(different path to brew if you're on Intel)

Doing this meant nvm install 14.20.0 completed without error (dependent on xcode-tools version which I raised in a different rejected bug report), and felt cleaner than using pyenv to achieve the same thing. As a bonus doing that makes also python resolve to python3 which is needed for certain other commands to work.

It would avoid a lot of issues if the node developers simply provided an ARM binary for Darwin on Node 14.20.0, but I guess that's not going to happen now.

Slightly off-topic: Does anyone know how I can create my own version of https://nodejs.org/dist/v14.20.0/ with my own node-v14.20.0-darwin-arm64.tar.gz with and get nvm to use it? It looks like it's signed. Then I'd only have to go through this once, upload the built binary somewhere and not need the above hacks when setting up a new machine.

from nvm.

@keeely you can host it somewhere and set the nodejs.org mirror env var to point to it, and nvm will look there instead.

from nvm.

@keeely you can host it somewhere and set the nodejs.org mirror env var to point to it, and nvm will look there instead.

Thanks! Yes, index.tab is needed, and then just the file in the right directory.

├── index.tab
└── v14.20.0
    └── node-v14.20.0-darwin-arm64.tar.xz

It gives a warning about the missing checksum but then goes on to install it.

$ NVM_NODEJS_ORG_MIRROR=http://localhost:8081 nvm install v14.20.0
Downloading and installing node v14.20.0...
Downloading http://localhost:8081/v14.20.0/node-v14.20.0-darwin-arm64.tar.xz...
######################################################################################################################################################## 100.0%
Computing checksum with sha256sum
Provided checksum to compare to is empty.

from nvm.

In case it's helpful, here's a precompiled binary for node 14.21.3 on M1 https://github.com/modderme123/node14-arm (I compiled this one using nix)

from nvm.