No matter if you are working on backend or are in the frontend camp, Node.js is getting more popular day by day and you may need to install it at some point. There is plenty of ways to install it on your operating system and I am about to show you the most popular methods and highlight pros and cons of each of them.

1. Brew Node
2. Brew Uninstall Node
3. Brew Node Version Manager

Pre-built installer for your platform #

Brew link node@8. Lastly, verify you have the right version installed using the node version command from the first step. (Note: If you downgrading to a lower version because of package issues on.

The easiest and most obvious way is to download a pre-built installer for your platform from the Node.js downloads page. Installation itself is very straight forward — next, next, next, done.

Despite the fact it is the easiest way of installing it, it comes with many disadvantages. It locks you to a particular version — it may not be a big issue on day one but it can be in the long run if you are willing to jump between projects that depend on different versions. Another (worst) issue with this method is the fact that it requires admin permissions (sudo) to install package globally. I published “Fix privileges and never again use sudo with npm” with some solutions for this issue, but you better check “Resolving EACCES permissions errors when installing packages globally” on official documentation or follow this article.

Node from Homebrew / Chocolatey #

“Homebrew — the best friend of the macOS user” explains why I love this tool so much. Windows users can find an alternative like Chocolatey. Both of these package managers allow you to install Node.js with ease.

CLI tools like that allow you to install / uninstall software in no time and never again be bothered by insufficient permissions. Although they allow you to manage versions too, in Node.js you should use…

NVM (Node Version Manager) #

1. Brew install node@8 Also remember that you can install more than 1 node package at the same time, but you cannot have them available at the same time. So if you have the latest/generic node package already installed you need to unlink it first: brew unlink node And then you can link a different version: brew link node@8.
2. Brew install node To test out your Node and npm install, try installing Grunt (you might be asked to run with sudo): npm install -g grunt-cli If that worked then congratulations — you’ve installed Node.js, npm, and Grunt.
3. Brew install node. F o r updating Node.js, you will need to use Node Version Manager. To check what version of NVM you have: nvm -v. If you don’t have NVM installed, or need to update it, run.

Node Version Manager is a simple bash CLI that allows you to install multiple Node.js versions and switch between them using simple commands. Although it is available for macOS and Linux only, Node.js version manager for Windows exists (ironically it is written in Go). Installation is straightforward — you can use a simple bash script or brew (my preferred way).

Thats the way to install the latest version of Node.js.

Be curious and explore more nvm commands on an official nvm documentation. My most frequently used commands are: install, uninstall, list and use.

It is hard to remember the version of Node.js that a project depends on — smash the version into .nvmrc file in the root of your project and run nvm use inside this directory. If something can be automated, it should be automated — installing the right version of dependencies is not an exception. I made a simple bash script that runs nvm use whenever it encounters a .nvmrc file inside your project. There is a cool zsh-nvm plugin for Zsh users that does the same job.

Brew Node

Do you use nvm by @creationix to manage @node versions? Have you ever forgotten to `nvm use` in your project? I have a little bash script for y'all. Put it into your .bashrc / .bash_profile and you are all set :-*https://t.co/GhVwRKYnw7#node#nodejs#nvm#js#javascriptpic.twitter.com/jWGN89rQnA

— Paweł Grzybek (@pawelgrzybek) January 12, 2019

• • I am glad it helped you out. Have a great day!

• thank you! definitely more detailed and nicer explained than other top google ranked posts on this topic. What are the most important reasons to use nvm over brew?

  • Hi.

    Thanks for nice words. The main reason why I use nvm is the fact that I work on multiple projects. Some of them are built with the latest node runtime, some of server-less lambda stuff that I work on is on 8.10. The ease of switching versions is extremely convenient. Other than that and if you always work with the latest version I would suggest being stick to `brew install node`.

    Have a great day 🥑

• Very helpful, thank you.

• It should be noted that installing nvm with Homebrew is not officially supported:

  Homebrew installation is not supported. If you have issues with homebrew-installed nvm, please brew uninstall it, and install it using the instructions below, before filing an issue.

  • Mikandi gold hack mod apk 2017. Yes you are right.

    The only reason why is the fact that nvm needs to be added to shell session. Official installation script does it for you. Brew installation requires a few lines of code to be added to .zshrc / .bashrc / .whareverrc..

    Post-install message from brew formula gives a detailed instruction about this step.

    Thanks for contribution. Have a fantastic day!

• Thank you. Now, I can move on with my Node.js course. Best wishes.

  • My pleasure. Good luck in your programming career!

• Thanks for share! Very useful information, just add the notes about the missing lines in the ~/.bash_profile that we should add when we install nvm through brew

  • Thanks a ton for suggestion. I will update this article at some point. Have a great day Enrique 🥑

What'ya think?

If you’re looking for an easy guide to install Node.js and npm on OS X and macOS — this is it.

Before we get started, are you listening to JS Party? If not, you should be! Maybe start with our episode all about best practices for Node developers. ✊

The default method for installing Node.js is to download a pre-built installer for your platform, install it and make sure it’s on your $PATH.

However, if you’re a Homebrew fan like me and prefer to install all of your packages with it — ensuring your packages are installed using the same commands and directories and allowing Homebrew to easily manage upgrades and updates — then this guide will help you get started.

Install Node.js and npm with Homebrew

First, install Homebrew.

Then run brew update Wartune test server. to make sure Homebrew is up to date.

As a safe measure you should run brew doctor to make sure your system is ready to brew. Run the command below and follow any recommendations from brew doctor.

Next, add Homebrew’s location to your $PATH in your .bash_profile or .zshrc file.

Next, install Node (npm will be installed with Node):

To test out your Node and npm install, try installing Grunt (you might be asked to run with sudo):

Brew Uninstall Node

If that worked then congratulations — you’ve installed Node.js, npm, and Grunt.

If not — retrace your steps or post a question to Stack Overflow.

Listen to related podcasts on The Changelog

Brew Node Version Manager

Since you’re interested in Node.js, npm, and Homebrew — listen to some recent related podcasts we’ve done on those subjects.