276

I've seen the writeup on using yum to install the dependencies, and then installing Node.JS & NPM from source. While this does work, I feel like Node.JS and NPM should both be in a public repo somewhere.

How can I install Node.JS and NPM in one command on AWS Amazon Linux?

sguler
  • 246
  • 1
  • 7
Tim Fulmer
  • 8,992
  • 4
  • 22
  • 32
  • [From the node.js website: Installing Node.js via package manager](https://nodejs.org/en/download/package-manager/#enterprise-linux-and-fedora) – iolsmit Dec 19 '17 at 01:13

18 Answers18

403

Stumbled onto this, was strangely hard to find again later. Putting here for posterity:

sudo yum install nodejs npm --enablerepo=epel

EDIT 3: As of July 2016, EDIT 1 no longer works for nodejs 4 (and EDIT 2 neither). This answer (https://stackoverflow.com/a/35165401/78935) gives a true one-liner.

EDIT 1: If you're looking for nodejs 4, please try the EPEL testing repo:

sudo yum install nodejs --enablerepo=epel-testing

EDIT 2: To upgrade from nodejs 0.12 installed through the EPEL repo using the command above, to nodejs 4 from the EPEL testing repo, please follow these steps:

sudo yum rm nodejs
sudo rm -f /usr/local/bin/node
sudo yum install nodejs --enablerepo=epel-testing

The newer packages put the node binaries in /usr/bin, instead of /usr/local/bin.

And some background:

The option --enablerepo=epel causes yum to search for the packages in the EPEL repository.

EPEL (Extra Packages for Enterprise Linux) is open source and free community based repository project from Fedora team which provides 100% high quality add-on software packages for Linux distribution including RHEL (Red Hat Enterprise Linux), CentOS, and Scientific Linux. Epel project is not a part of RHEL/Cent OS but it is designed for major Linux distributions by providing lots of open source packages like networking, sys admin, programming, monitoring and so on. Most of the epel packages are maintained by Fedora repo.

Via http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/

Matthew Herbst
  • 21,357
  • 19
  • 68
  • 107
Tim Fulmer
  • 8,992
  • 4
  • 22
  • 32
  • 8
    This is definitely the fastest approach I've seen, but a warning may be useful -- the EPEL repository isn't in sync with the current stable node, and you can't use "n" to fix that when it's been installed this way (at least, not without some kind of magic that's beyond me). The tedious git clone / make install approach is the only way I've found to ensure a consistent and current install. – Semicolon Mar 15 '15 at 17:12
  • 23
    I got node 0.10.36 and npm 1.3.6 out of this. These are very out of date. – voltrevo Sep 19 '15 at 04:44
  • 4
    @Semicolon you can get around that by only installing npm, then `sudo npm install -g n` and `sudo n v0.12` or whatever other version you like. – unboundev Oct 06 '15 at 02:39
  • 2
    If using AWS linux and this method, do NOT use n. Instead use `nvm` to upgrade to the latest version. `n` doesn't upgrade as expected. – RandomDeduction Oct 30 '15 at 13:57
  • 1
    @RandomDeduction's comment fixed it for me. Tried `n` before and didn't work. [`nvm's github page`](https://github.com/creationix/nvm) - for AWS linux (Amazon Linux) use `cURL` and then simply `nvm install 5.0` (latest as of now). – Neta Nov 10 '15 at 15:02
  • 4
    n update as expected, but it does not update the node link properly. You'll have to run the extra command : `sudo ln -sf /usr/local/n/versions/node//bin/node /usr/bin/node` – Masadow Nov 25 '15 at 14:18
  • @Masadow You shall live 100 years for this kind gesture Sir! Thanks a lot. – Zeno Popovici Dec 15 '15 at 21:16
  • 4
    this answer didn't work since `sudo yum install nodejs --enablerepo=epel-testing` returns the error: "No package nodejs available." while `sudo yum install nodejs --enablerepo=epel` only gave very old versions... – goredwards May 11 '16 at 23:53
  • Another option. I did `sudo yum install nodejs npm --enablerepo=epel` and then I installed https://github.com/creationix/nvm and used it to install other versions of node. – nackjicholson Aug 07 '16 at 22:53
  • very old node version, not recommended – Miao ZhiCheng Apr 26 '18 at 06:09
252

Like others, the accepted answer also gave me an outdated version.

Here is another way to do it that works very well:

$ curl --silent --location https://rpm.nodesource.com/setup_14.x | bash -
$ yum -y install nodejs

You can also replace the 14.x with another version, such as 16.x, 12.x, etc.

You can see all available versions on the NodeSource Github page, and pull from there as well if desired.

Note: you may need to run using sudo depending on your environment.

Matthew Herbst
  • 21,357
  • 19
  • 68
  • 107
  • 4
    This is what I needed to use on AWS Elastic Beanstalk to get a more recent version than that already installed. – Jon Burgess Feb 10 '16 at 00:45
  • 1
    Works just perfect while I need to run `npm install` for `package.json`, – Chetabahana Feb 26 '16 at 16:18
  • 38
    I needed to run this with `curl --silent --location https://rpm.nodesource.com/setup_4.x | sudo bash -` – user465342 Mar 25 '16 at 02:44
  • 19
    If you get permission denied, you'll need to add some sudo. `curl --silent --location https://rpm.nodesource.com/setup_6.x | sudo bash -` and `sudo yum -y install nodejs` – sampoh Apr 20 '17 at 11:29
  • Two issues: 1 - you forgot sudo. 2 - this requires two commands, but your text makes it look like one command. The correct answer is: `$ curl --silent --location https://rpm.nodesource.com/setup_6.x | sudo bash -` and then `$ sudo yum -y install nodejs`. Don't enter the $ sign obviously, thats just your command prompt. – JK. Aug 10 '17 at 00:54
  • 1
    if you wanna install Node.js 8.x, shoud execute `curl --silent --location https://rpm.nodesource.com/setup_8.x | bash -` – Argun Aug 31 '17 at 13:01
  • how do i install 6 to install 7 or 8 if i have already use this method to install 6? i tried install adding the 7 nodesource and uninstalling nodejs and npm and reinstalling but it still installs 6. – PK. Dec 06 '17 at 11:48
64

The accepted answer gave me node 0.10.36 and npm 1.3.6 which are very out of date. I grabbed the latest linux-x64 tarball from the nodejs downloads page and it wasn't too difficult to install: https://nodejs.org/dist/latest/.

# start in a directory where you like to install things for the current user
(For noobs : it downloads node package as node.tgz file in your directlry)
curl (paste the link to the one you want from the downloads page) >node.tgz

Now upzip the tar you just downloaded -

tar xzf node.tgz

Run this command and then also add it to your .bashrc:

export PATH="$PATH:(your install dir)/(node dir)/bin"

(example : export PATH ="$PATH:/home/ec2-user/mydirectory/node/node4.5.0-linux-x64/bin")

And update npm (only once, don't add to .bashrc):

npm install -g npm

Note that the -g there which means global, really means global to that npm instance which is the instance we just installed and is limited to the current user. This will apply to all packages that npm installs 'globally'.

Darpan
  • 5,193
  • 3
  • 45
  • 74
voltrevo
  • 8,223
  • 3
  • 23
  • 25
  • 4
    This is actually the best answer, as you get exactly the version you want – Mariusz Nov 23 '15 at 01:39
  • 1
    Wish I'd read this answer first - this should be the accepted answer because you can choose which version you want to install. -- thank you @voltrevo – Mike W Nov 25 '15 at 10:11
  • 2
    @voltrevo thank you for the answer. Yes, there are other ways to install node on Linux. The accepted answer is a one-liner, which happens to plug into the YUM package system for automated and managed updates. The packages in the YUM repos do tend to be a little bit older, and are also a bit better tested with wider deployments. Personally, I recommend leaving the latest and greatest to local development environments, and use something more like the accepted answer for production environments. Cheers! – Tim Fulmer Jan 18 '16 at 22:00
  • for old centos versions this is the best way to go – user1336321 Mar 09 '16 at 15:09
  • Error after running node -v now is: 'cannot execute binary file'. Any ideas? – Jos Faber Nov 24 '16 at 14:20
  • @JosFaber Hmm this might happen if you download node for a different architecture. You probably want the one that ends in `-linux-x64.tar.gz `. – voltrevo Nov 27 '16 at 23:25
33

Simple install with NVM...

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash
. ~/.nvm/nvm.sh
nvm install node

To install a certain version (such as 12.16.3) of Node change the last line to

nvm install 12.16.3

For more information about how to use NVM visit the docs: https://github.com/nvm-sh/nvm

fuzzysearch
  • 638
  • 8
  • 14
  • 1
    This totally works. Takes less time than @goredwards answer too. Tried on an Amazon ECS optimized AMI. – Jayant Bhawal Aug 17 '16 at 10:41
  • 3
    The accepted answer and all of the EDITs 1-3 didn't work for me, but this worked. Thanks! – seantomburke Aug 23 '16 at 15:19
  • 1
    neat and compact. – Stephen Tetreault Feb 08 '17 at 18:55
  • 1
    simple and awesome – Abhinav Feb 17 '17 at 09:27
  • 2
    This should be the answer. It's best best by far unless someone is looking to build from source. – Kirkland Feb 20 '17 at 15:22
  • 1
    This will not work if you are using userdata via cloudformation's AWS::EC2::LaunchTemplate.. it wil lwork if you SSH into your EC2 and run it. I'm still stuck on getting it to work via userdata – newbreedofgeek Feb 21 '19 at 07:38
  • But can I get a global install? I want "node" in /usr/bin, or the like. Everything I have read, (plus some non-definitive experience) suggests "nvm" wants to install node locally, and then modify my personal PATH so that I personally can find it. But for me, a "global" install, when referring to a CLI, means that all users have access to the executable, without a special PATH modification. (Contrast w regards to a lib in node_modules for "nvm/npm", the word "global"can mean "global to one user".) I am not confident that the "nvm" solution allows for system global. Anybody know for sure? – IAM_AL_X May 08 '21 at 05:56
29

The procedure that worked for me (following these rather old instructions with a few updates):

  • check git is installed git --version or install it via:
    sudo yum install git
  • install gcc and openssl:
    sudo yum install gcc-c++ make
    sudo yum install openssl-devel
  • clone the git repo into a directory called node (which you can remove later):
    git clone https://github.com/nodejs/node.git
  • decide which version of node you want at https://github.com/nodejs/node/releases
  • go to the node directory just created and install node
    cd node
    git checkout v6.1.0 - put your desired version after the v
    ./configure
    make
    sudo make install
  • test that node is installed / working with either node --version or simply node (exit node via process.exit() or ^C x 2 or ^C + exit)
  • check the npm version: npm --version and update if necessary via sudo npm install -g npm
  • Optional: remove the node directory with rm -r node

Notes:

  1. The accepted answer didn't work since sudo yum install nodejs --enablerepo=epel-testing returns the error: No package nodejs available.
    ...and sudo yum install nodejs --enablerepo=epel (ie without -testing) only gave very old versions.
  2. If you already have an old version of node installed you can remove it with:
    sudo npm uninstall npm -g ...since npm can uninstall itself
    sudo yum erase nodejs
    sudo rm -f /usr/local/bin/node
    (sudo yum rm nodejs in the accepted answer won't work as rm is not a valid yum command see yum --help)
  3. It's possible to clone the node repo via git clone git://github.com/nodejs/node.git rather than git clone https://github.com/nodejs/node.gitbut you may get a various errors (see here).
  4. If you already have a /node dir from a previous install, remove it before using the git clone command (or there'll be a conflict):
    rm -r node
  5. If you have trouble with any sudo npm... command - like sudo: npm: command not found and/or have permissions issues installing node packages without sudo, edit sudo nano /etc/sudoers and add :/usr/local/bin to the end of the line Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin so that it reads Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
goredwards
  • 2,296
  • 2
  • 26
  • 39
  • 4
    @Gio plenty of other answers to choose from if this one doesn't please you ;-) ...'in one command' wasn't the most important part of the question IMHO. – goredwards Jun 28 '16 at 13:36
  • This is very useful after I made a mistake with the accept answer. Thank you – Daron Tancharoen Nov 03 '16 at 05:46
  • @talentedandrew the `etc/sudoers` file controls who can run what commands as what users on what machines - but will only run / find / look for commands that are in directories listed on its `secure_path` Node should be installed in `/usr/local/bin` and if it's there sudo should find it - see http://stackoverflow.com/a/31734090/3092596 If sudo doesn't find it, then that path needs to be added to sudo's `secure_path` - see also: http://superuser.com/a/927599/404543 – goredwards Jan 20 '17 at 22:18
  • I would like to add that you might have to fix your symbolic links after you install using this method: `sudo ln -s /usr/local/bin/node /usr/bin/node sudo ln -s /usr/local/lib/node /usr/lib/node sudo ln -s /usr/local/bin/npm /usr/bin/npm sudo ln -s /usr/local/bin/node-waf /usr/bin/node-waf` – BuffMcBigHuge Sep 25 '17 at 18:10
19

For the v4 LTS version use:

curl --silent --location https://rpm.nodesource.com/setup_4.x | bash -
yum -y install nodejs

For the Node.js v6 use:

curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -
yum -y install nodejs

I also ran into some problems when trying to install native addons on Amazon Linux. If you want to do this you should also install build tools:

yum install gcc-c++ make
Niklas R.
  • 22,209
  • 67
  • 202
  • 380
birnbaum
  • 3,690
  • 23
  • 35
  • This is a fantastic answer. It no longer takes me 20 minutes to install Node anymore. – David Webber Apr 29 '16 at 18:07
  • if you run a php application with some npm compiled frontend on elastic beanstalk, you may use this. it's part of my install.config file that made it work -- https://gist.github.com/marekjalovec/1ccee0c2254e65fc5d82eb35c7da82ae – Marek Jalovec May 22 '16 at 22:26
14

I just came across this. I tried a few of the more popular answers, but in the end, what worked for me was Amazon's quick setup guide.

Tutorial: Setting Up Node.js on an Amazon EC2 Instance

The gist of the tutorial is:

  1. Make sure you are ssh'd onto the instance.
  2. Grab nvm: curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash
  3. Active . ~/.nvm/nvm.sh
  4. Install node using nvm nvm install 4.4.5 (NOTE: You can choose a different version. Check out the remote versions first by running $ nvm ls-remote)
  5. Finally, test that you have installed node Node correctly by running $ node -e "console.log('Running Node.js' + process.version)"

Hopefully this helps the next person.

troxwalt
  • 334
  • 3
  • 10
  • You might want to explain te content in that link. A good answer only uses a link as a reference, not the main topic of the answer. – BusyProgrammer Feb 21 '17 at 22:02
12

Seems no one is mentioning this. On Amazon Linux 2, official way to load EPEL is:

  • sudo amazon-linux-extras install epel

...then you may:

  • sudo yum install nodejs

     

See Extras Library (Amazon Linux 2)

theaws.blog
  • 2,001
  • 20
  • 19
6

I had Node.js 6.x installed and wanted to install Node.js 8.x.

Here's the commands I used (taken from Nodejs's site with a few extra steps to handle the yum cached data):

  1. sudo yum remove nodejs: Uninstall Node.js 6.x (I don't know if this was necessary or not)
  2. curl --silent --location https://rpm.nodesource.com/setup_8.x | sudo bash -
  3. sudo yum clean all
  4. sudo yum makecache: Regenerate metadata cache (this wasn't in the docs, but yum kept trying to install Node.jx 6.x, unsuccessfully, until I issued these last two commands)
  5. sudo yum install nodejs: Install Node.js 8.x
Brad W
  • 190
  • 3
  • 5
3

sudo yum install nodejs npm --enablerepo=epel works for Amazon Linux AMI. curl --silent --location https://rpm.nodesource.com/setup_6.x | bash - yum -y install nodejs works for RedHat.

Devs love ZenUML
  • 9,490
  • 7
  • 41
  • 55
2

The easiest solution is this( do these as root)

sudo su root
cd /etc
mkdir node
yum install wget
wget https://nodejs.org/dist/v9.0.0/node-v9.0.0-linux-x64.tar.gz
tar -xvf node-v9.0.0-linux-x64.tar.gz
cd node-v9.0.0-linux-x64/bin
./node -v
ln -s /etc/node-v9.0.0-linux-x64/bin/node node

enter image description here

grepit
  • 16,512
  • 5
  • 83
  • 71
2

https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

curl --silent --location https://rpm.nodesource.com/setup_10.x | sudo bash - sudo yum -y install nodejs

Sunil Buddala
  • 787
  • 1
  • 8
  • 20
1

Official Documentation for EC2-Instance works for me: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html

 1. curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash
 2. . ~/.nvm/nvm.sh
 3. nvm ls-remote (=> find your version x.x.x =>) nvm install  x.x.x
 4. node -e "console.log('Running Node.js ' + process.version)"
0

As mentioned in official documentation , simple below 2 steps -

curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt-get install -y nodejs
Vivek Chaturvedi
  • 450
  • 5
  • 15
0

For those who want to have the accepted answer run in Ansible without further searches, I post the task here for convenience and future reference.

Accepted answer recommendation: https://stackoverflow.com/a/35165401/78935

Ansible task equivalent

tasks:
  - name: Setting up the NodeJS yum repository
    shell: curl --silent --location https://rpm.nodesource.com/setup_10.x | bash -
    args:
      warn: no
  # ...
Andrei Cioara
  • 2,384
  • 2
  • 23
  • 46
0

You can update/install the node by reinstalling the installed package to the current version which may save us from lotta of errors, while doing the update.

This is done by nvm with the below command. Here, I have updated my node version to 8 and reinstalled all the available packages to v8 too!

nvm i v8 --reinstall-packages-from=default

It works on AWS Linux instance as well.

0

I usually use NVM to install node on server. It gives me option to install multiple version of nodejs. Commands are given below

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash

then check if it's install properly

command -v nvm

after that, run this to install latest version

nvm install node

or

nvm install 11

  • Thanks for your answer! Please be careful piping code retrieved from the internet directly into `bash`, you may expose yourself to exploits doing this. I would suggest downloading the source first and making sure it contains the script you expect. – Exelian Sep 22 '20 at 12:36
  • Thanks for your comment. – Atiqur Rahman Sep 22 '20 at 13:38
0

As others mentioned using epel gives a really outdated version, here is a little script I just wrote instead to add to the CI pipeline or pass it to ec2 user-data to install the latest version of node, simply replace the version with what you want, and the appropriate distro of Linux you are using.

The following example is for amazon-Linux-2-AMI

#!/bin/bash

version='v14.13.1'
distro='linux-x64'
package_name="node-$version-$distro"
package_location="/usr/local/lib/"

curl -O https://nodejs.org/download/release/latest/$package_name.tar.gz
tar -xvf $package_name.tar.gz -C $package_location
rm -rfv $package_name.tar.gz

echo "export PATH=$package_location/$package_name/bin:\$PATH" >> ~/.profile

if you want to test it in the same shell simply run

. ~/.profile
Mo Hajr
  • 974
  • 1
  • 11
  • 27