Is it normal that nvm install 10 for the first time takes more than an hour?

[johhansantana]

I created a VPS with Ubuntu 14.04 LTS 32bit and after installing nvm via curl I have ran:
nvm install 10 and it's taking a lot longer than usual. These are the logs:

It's neverending logging similar things.

I remember this happening once on my personal computer a long time ago when I had ubuntu installed as well but it has never happened again until today.

[ljharb]

It definitely isn’t normal.

It looks like it’s hanging on the compilation step - is there any chance you copied the .nvm dir from a different machine? If so, try nvm cache clear and try the install again?

If not, then I’m really not sure - presumably the same issue would occur with compiling node downloaded directly from the website.

[johhansantana]

After trying nvm cache clear and nvm install 10 I got the same result ( I think )

Here's are the logs:
https://gist.github.com/johhansantana/3f68b41b82811c291bb406bab0b4c3d9

I tried installing V9.x using nvm install 9 and it worked :l

[ljharb]

It's possible that node v10 isn't compatible with your machine - is it 32 bit or 64 bit? What exact architecture are you on?

[ljharb]

Also, what gcc version do you have?

[johhansantana]

It is 32bit.

Not sure what you mean by gcc

[ljharb]

gcc --version - it's the C compiler. node no longer produces 32 bit binaries as of v10, so you'd have to be able to compile it from source. (32 bit machines are very very ancient)

[ljharb]

So given that it's compiling, and that it's an old slow machine, and that v9 didn't have to compile, i think it might actually be normal for it to take multiple hours to install.

[ljharb]

See nodejs/build#1498 - looks like it's not reliable to be able to use node on 32 bit machines on v10+.

[ashrafulislambd]

It's not an error. 32 bit binaries are not available. So nvm is compiling it from source. Run it again and wait. It works fine. It compiles and you have to restart. Then you have to type.

nvm use 10.0.0 # or the version you use

[MirroringCode]

I know this post is really old, but i hope the author or another user could tell me if this issue was solved, because i have the same problem trying to install newer versions of node in my laptop, it just display that same message and i don't know if i should just leave it downloadiing or what else to do.

If the author is seeing this... did it worked? I mean, it installed node after a while? Thanks in advance.

[johhansantana]

I know this post is really old, but i hope the author or another user could tell me if this issue was solved, because i have the same problem trying to install newer versions of node in my laptop, it just display that same message and i don't know if i should just leave it downloadiing or what else to do.

If the author is seeing this... did it worked? I mean, it installed node after a while? Thanks in advance.

As the comments stated here I believe it worked (can't remember).

[mark-tripney]

👋 If anyone revisits this: I just downgraded to 15.14.0 via NVM (owing to issues with 16.* on Silicon Macs), and experienced the OP's issue. The install took about 10 minutes, but was, ultimately, fine.

[ljharb]

@mtripney ftr, node 16+ is the only one that supports M1 macs natively; everything else uses Rosetta emulation.

[blairbodnar]

Thanks for noting this @mtripney - Took me about 10 minutes as well installing 12.22.1 via NVM on a new Silicon Mac. I was about to bail out but then saw your comment and waited :)

[mark-tripney]

@blairbodnar Glad it helped!

[mark-tripney]

@ljharb You're right, of course, but I’ve had no end of problems with v16, such that I eventually had to downgrade. (One critical example being: vercel/next.js#24564)

[ghost]

👋 If anyone revisits this: I just downgraded to 15.14.0 via NVM (owing to issues with 16.* on Silicon Macs), and experienced the OP's issue. The install took about 10 minutes, but was, ultimately, fine.

can confirm this. just set up my M1 with v15 and it took quite a bit (enough for me to reach this thread) but was, ultimately, fine.

[ViliRan]

Can confirm, went to 12.14.1 on a M1 MacBook Pro. Took about 10 minutes, even spun up the fans for the first time ever. But it did finish and is seemingly fine.

[BrianM0330]

Another confirmation here. M1 MacBook Air on Monterey, downgrading to Node 14 for a project I'm working on and after 10 or so minutes everything finished.

Don't close it out!

[ricardocamacho]

I can also confirm it worked for me on Macbook Air M1 chip Monterey, after more than 10 minutes, however, it took about 10 GB of space in disk, is this normal?

[ljharb]

@ricardocamacho That's a question to ask node itself; nvm doesn't have any interaction beyond automating the node compilation process.

[Qarun-Qadir-Bissoondial]

It seems that I previously had nvm installed through Home-brew. I uninstalled it, created a rosetta-specific terminal and installed my node versions from there
Everything worked fine when I did that

[pascalstockert]

Can confirm that this works on an M2 MacBook as well - just takes a little time, but ultimately the compilation succeeds and v14.18.1 was installed.

[sachinmankotia1991]

I tried installed version 16 and for me also, it took 20+ mins but in the end , it was done

[IliaZolas]

took me almost an hour but it finally worked 😅 (Intel macbook pro touch, node v16.20.2)

[ddohcim]

it took about 25 min upgrading from node 16.18.1 to 18.18.0 on my M1 Pro, I also confirm everything went successful

[URobert]

Can also confirm it took a long time (10min+) on M2. This was installing version 20

[lazysergey]

I must say this thread is a gem, I was going to interrupt the installer before reading this
my experience - 14.17.0 took around 10min on M2, works completely fine, just grab some coffee and wait

[bashers222]

Using this method to install NVM10 on my pi2 (which is possible it seems.)
Its still compiling after 6 hours!

[karnatik]

Using this method with v20.11.1, more than 6 hours on Pi Zero WH..canceled :(
Trying with v16.20.2 after clearing manually : ~/.nvm/.cache/node-v20.11.1 to free 800Mo :
=> 4hours later :
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[1]: *** [tools/v8_gypfiles/v8_base_without_compiler.target.mk:994: /home/user/.nvm/.cache/src/node-v16.20.2/files/out/Release/obj.target/v8_base_without_compiler/deps/v8/src/api/api.o] Error 1
..will try something else so..