nvm for installing node, npm, and switching node versions.

Homebrew for installing command line utilities on Mac.

It so you know what to do if this happens to you.īefore you get started, I recommend you install three things on your However, when I re-cloned the repo for this blog and Software built for Intel-based Macs, but I figured all of that would I heard that there were some issues with software compatibility with

I got the basic Macbook Air but with 16 GB of RAM if you're wondering. My advice to you is to start with the first method and see how far it gets you.I just bought a new Macbook with an M1 chip to work on my Starting over just felt like a simpler path for me with a new machine. I'm confident I would have eventually gotten to a working situation using Rosetta. It became a whole thing and, because I had just opened my computer, I ended up wiping it and starting clean.

But Homebrew updated for the new chip and now installs libraries in a different location. Because Node relies on other libraries, I also needed the appropriate versions of those libraries, too. It wasn't just a matter of open Terminal differently and reinstalling Node.

But, starting the process was opening a can of worms. See here for more info.Īfter going down this route, it's felt safer. To run your terminal application in compatibility mode, set it to Open using Rosetta, then reinstall node versions. It's build specifically to ease the transition to Apple's new chip. Rosetta is a environment that translates executables to be able to run on the Apple M1 chip. Method #2: Run in Compatibility ModeĪnother option is to run your terminal in compatibility mode using Rosetta. I still run into intermittent issues with v15, so I don't feel like this is a foolproof solution. I even tried v14 just to see what would happen, and sure enough, I also ran into issues with it. Our team uses NVM (Node Version Manager) to install and manage multiple node versions. I found this discussion which noted that Node.js versions prior to v15 do not natively support the Apple M1 chip. I've since come across two methods for solving this issue. It began occurring regularly enough that I started digging. I was working with our fancy new CLI tool with my fancy new MacBook Pro with the M1 chip when I came across this scary error, courtesy of Node.js: FATAL ERROR: wasm code commit Allocation failed - process out of memory

Nvm m1 mac