If you've done everything correctly, you should be able to run the nvm command and ask it to list which versions node are available. vim ~/.bash_profileĮxecute the content we just pasted. Step 3: Configure your environmental variablesĮither create or open your.
Step 2: Create a directory for NVM mkdir ~/.nvm/ This short article describes how to install Homebrew or visit the Homebrew website You install NVM using Homebrew, and if you don't have Homebrew installed yet, read this article. Switching back to, let’s say, version 12 would be as easy as nvm use 12.Node Version Manager makes it easy to install multiple Node versions on a Mac. If you have multiple versions and you want to specify which version you would like to use, simply use: nvm use 11 To see what Node versions are available to install run: nvm ls-remoteįor me, I just needed the latest point release of Node version 11 so I ran nvm install 11Īfter installing you can verify what is installed with nvm ls Now running nvm -v should return nvm’s options. Now either quit and reopen your Terminal, or run source ~/.bash_profileĮchoing $NVM_DIR should now return your NVM directory :$ echo $NVM_DIR Now add these lines to ~/.bash_profile ( or ~/.zshrc for macOS Catalina or later) export NVM_DIR=~/.nvm If you don’t have Homebrew installed, install it now.Īfter installing it, update the Homebrew package list and install NVM. I had Node installed via Homebrew and found that I needed to first uninstall node. If you already have node installed, uninstall it.
I’ll admit I was hesitant that I would fall into a serious rabbit hole and divert too much time away from my task at hand, but it turned out to be really simple so I thought I’d share it with you all. An alternative to this I saw was to npm install on Node version 11.Ī friend’s suggestion to try NVM to easily switch between Node environments popped into my head. So yesterday I was in the process of installing dependencies for a Gatsby tutorial project when I hit some build errors while installing NPM packages.Īfter pouring over Github issues, I found a work around that was rather wonky.
0 kommentar(er)
