Gal Schlezinger

Greetings, do you want to install latest, or latest LTS version? (the latter is what I generally recommend)

@jurajpiar this is not confusion, we install a rosetta version because Node.js does not provide a prebuilt ARM binaries for Mac for 14.x: https://nodejs.org/dist/v14.20.0/

for the original thread: I don't understand why people will use x64 and run through Rosetta when they can install an ARM version?

I'm closing this as this is a known issue. Sorry that this is how it resolves @jurajpiar, hope that we won't have any issues like this in the future :pray:

Hmm. Seems like Bash is caching the full paths. `hash -r` should fix that. ```sh-session $ eval "$(fnm env --use-on-cd)" Using Node v12.20.1 $ fnm use 14 Using Node v14.15.1...

That's a good question. I think we provide `FNM_ARCH` with `fnm env`, so the users pass `--arch` implicitly with environment variables. Maybe we need to set `FNM_FORCE_ARCH`? Maybe we need...

So anyway I think that the change will not be trivial, but we might want to alter the behavior to look for the files that the node version index provides.

> Ran into this today, it seems 14 does have arm builds it does not :thinking: i.e. latest version: https://nodejs.org/dist/v14.20.0/ does not have arm builds _for darwin_, which is what...

I was very much opposing the idea of compiling versions on the fly because it is _extremely_ slow, so I wanted to add `fnm install --compile-if-needed` or `fnm env --compile-if-needed`...

I had a thought while driving: what if we had `fnm import-installation ./my-self-compiled-node-directory`?