Node Version Manager (https://github.com/nvm-sh/nvm) works perfectly across native node installations as well as emulated Rosetta installations. The trick I am using here is to install one LTS version of node under Rosetta and another stable version as native binary.
| # Run the install command from a native (ARM) terminal | |
| # See https://github.com/nvm-sh/nvm#installing-and-updating | |
| curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash | |
| # Alternatively install using brew (officially unsupported by nvm): | |
| # brew install nvm | |
| # Don't forget to source the command in your shell profile to make it available in new terminals! |
| # From Rosetta Terminal (tick checkbox in Terminal right click menu -> Get Info -> Open using Rosetta) | |
| # To verify you are running in Rosetta run: | |
| arch | |
| -> i386 | |
| # Install node | |
| nvm install lts/fermium | |
| # Verify node installation | |
| nvm use lts/fermium | |
| node -e 'console.log(process.arch)' | |
| -> x64 |
| # From native Terminal | |
| # To verify you are running natively: | |
| arch | |
| -> arm64 | |
| # Install node | |
| nvm install stable | |
| # Verify node installation | |
| nvm use stable | |
| node -e 'console.log(process.arch)' | |
| -> arm64 |
| # To make DX a bit better you can alias your installations: | |
| nvm alias arm stable | |
| # arm -> stable (-> v15.6.0) | |
| nvm alias intel lts/fermium | |
| # intel -> lts/fermium (-> v14.15.4) | |
| # To test aliases: | |
| nvm use arm | |
| # Now using node v15.6.0 (npm v7.4.0) | |
| node -e 'console.log(process.arch)' | |
| -> arm64 | |
| nvm use intel | |
| # Now using node v14.15.4 (npm v6.14.10) | |
| node -e 'console.log(process.arch)' | |
| -> x64 |
Could someone elaborate on line 6?
# Don't forget to source the command in your shell profile to make it available in new terminals!
Does that mean to add something to my .zshrc? If so, what exactly would I be putting there? Based on https://github.com/nvm-sh/nvm#installing-and-updating shouldn't this be added already by running the curl command?
I'm going to follow this guide, but I already have a few questions about step 1, so I'm assuming I'll run into a lot of trouble.
I'm also assuming others might have similar questions, so I'm going to read through the steps, post my questions, and then I'm going to follow the guide and try to answer them and/or post more questions.
Run the install command from a native (ARM) terminal
See https://github.com/nvm-sh/nvm#installing-and-updating
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
curl -o command is the "install command"? Or are there preliminary steps I should take that I will find in "See https://github.." and therefore I should read the github link first? If so should I read the whole thing?Alternatively install using brew (officially unsupported by nvm):
brew install nvm
Don't forget to source the command in your shell profile to make it available in new terminals!
source <something>, but which directory should I be in? What exactly should I source? Should I follow what @serobalino did and do source ~/.nvm/nvm.sh?Install node
nvm install lts/fermium
Verify node installation
nvm use lts/fermium
node -e 'console.log(process.arch)'
-> x64
From native Terminal
To verify you are running natively:
arch
-> arm64Install node
nvm install stableVerify node installation
nvm use stable
node -e 'console.log(process.arch)'
-> arm64
To make DX a bit better you can alias your installations:
nvm alias arm stable
arm -> stable (-> v15.6.0)
nvm alias intel lts/fermium
intel -> lts/fermium (-> v14.15.4)To test aliases:
nvm use arm
Now using node v15.6.0 (npm v7.4.0)
node -e 'console.log(process.arch)'
-> arm64
nvm use intel
Now using node v14.15.4 (npm v6.14.10)
node -e 'console.log(process.arch)'
-> x64
Okay, I've overwhelmed myself so I won't answer all my own questions, but I did manage to follow this guide successfully, so here are a few answers:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash is the install command, I verified that by reading the link, and it worked out for mecurl command.source ~/.nvm/nvm.sh
These instructions seem to have worked for me but I'm still not able to connect to an oracledb using my M1 Mac. I created this simple repo. If anyone is willing to take a look and tell me where I'm going wrong, I would really appreciate it.
Update: I was able to resolve the issue and will update the repo I linked in the next few days.
This super helpful and tricky thank a lot.
thanks a lot brother!
@GoonerBrian Thanks a lot brother, I've been trying to fix this issue for the past 12hrs in my mac m1. Nothing really worked until i saw your repo. I really appreciate it❤️, its 3am here I can finally sleep now!!
@AmrMekkawy glad I could help! Sleep well.
Thank you, working expected.
As a note, this is not needed if you are installing node 16+
Anyone notice M1 doesn't run node as fast as x86? I had a machine from 2016 with far weaker specs on paper then my current machine, and my current set up does all things node related alot slower.