Want to take your software engineering career to the next level? Join the mailing list for career tips & advice Click here


NodeSource Node.js Binary Distributions

Subscribe to updates I use distributions

Statistics on distributions

Number of watchers on Github 7120
Number of open issues 86
Average time to close an issue 3 days
Main language Shell
Average time to merge a PR 7 days
Open pull requests 29+
Closed pull requests 51+
Last commit 25 days ago
Repo Created almost 6 years ago
Repo Last Updated 15 days ago
Size 778 KB
Organization / Authornodesource
Page Updated
Do you use distributions? Leave a review!
View open issues (86)
View distributions activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
Evaluating distributions for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

NodeSource Node.js Binary Distributions



This repository contains documentation for using the NodeSource Node.js Binary Distributions via .rpm, .deb and Snap packages as well as their setup and support scripts.

If you are looking for NodeSource's low-impact Node.js performance monitoring platform, please get started here.

Please file an issue if you are experiencing a problem or would like to discuss something related to the distributions.

Pull requests are encouraged if you have changes you believe would improve the setup process or increase compatibility across Linux distributions.

Table of Contents

Debian and Ubuntu based distributions

Available architectures:

NodeSource will continue to maintain the following architectures and may add additional ones in the future.

  • i386 (32-bit)not available for Node.js 10 and later
  • amd64 (64-bit)
  • armhf (ARM 32-bit hard-float, ARMv7 and up: arm-linux-gnueabihf)
  • arm64 (ARM 64-bit, ARMv8 and up: aarch64-linux-gnu)

Supported Ubuntu versions:

NodeSource will maintain Ubuntu distributions in active support by Canonical, including LTS and the intermediate releases.

  • Ubuntu 14.04 LTS (Trusty Tahr) - not available for Node.js 10 and later
  • Ubuntu 16.04 LTS (Xenial Xerus)
  • Ubuntu 18.04 LTS (Bionic Beaver)
  • Ubuntu 18.10 (Cosmic Cuttlefish)
  • Ubuntu 19.04 (Disco Dingo)
  • Ubuntu 19.10 (Eoan Ermine)
  • Ubuntu 20.04 LTS (Focal Fossa)

Supported Debian versions:

NodeSource will maintain support for stable, testing and unstable releases of Debian, due to the long release cycle a considerable number of users are running unstable.

  • Debian 8 / oldoldstable (Jessie)
  • Debian 9 / oldstable (Stretch)
  • Debian 10 / stable (Buster)
  • Debian unstable (Sid)

Supported Linux Mint versions:

  • Linux Mint 17 Qiana (via Ubuntu 14.04 LTS) - not available for Node.js 10 and later
  • Linux Mint 17.1 Rebecca (via Ubuntu 14.04 LTS) - not available for Node.js 10 and later
  • Linux Mint 17.2 Rafaela (via Ubuntu 14.04 LTS) - not available for Node.js 10 and later
  • Linux Mint 18 Sarah (via Ubuntu 16.04 LTS)
  • Linux Mint 18.1 Serena (via Ubuntu 16.04 LTS)
  • Linux Mint 18.2 Sonya (via Ubuntu 16.04 LTS)
  • Linux Mint 18.3 Sylvia (via Ubuntu 16.04 LTS)
  • Linux Mint Debian Edition (LMDE) 2 Betsy (via Debian 8)
  • Linux Mint 19 Tara (via Ubuntu 18.04 LTS)
  • Linux Mint 19.1 Tessa (via Ubuntu 18.04 LTS)
  • Linux Mint 19.2 Tina (via Ubuntu 18.04 LTS)
  • Linux Mint 19.3 Tricia (via Ubuntu 18.04 LTS)
  • Linux Mint 20 Ulyana (via Ubuntu 20.04 LTS)
  • Linux Mint Debian Edition (LMDE) 3 Cindy (via Debian 9)
  • Linux Mint Debian Edition (LMDE) 4 Debbie (via Debian 10)

Supported Devuan versions:

  • Jessie / oldstable (via Debian 8)
  • Ascii / stable (via Debian 9)
  • Beowulf / testing (via Debian 10)
  • Ceres / unstable (via Debian unstable)

Supported elementary OS versions:

  • elementary OS Freya (via Ubuntu 14.04 LTS) - not available for Node.js 10 and later
  • elementary OS Loki (via Ubuntu 16.04 LTS)
  • elementary OS Juno (via Ubuntu 18.04 LTS)
  • elementary OS Hera (via Ubuntu 18.04 LTS)

Supported Trisquel versions:

  • Trisquel 7 Belenos (via Ubuntu 14.04 LTS) - not available for Node.js 10 and later
  • Trisquel 8 Flidas (via Ubuntu 16.04 LTS)

Supported BOSS versions:

  • BOSS 5.0 Anokha (via Debian 7) - not available for Node.js 10 and later
  • BOSS 6.0 Anoop (via Debian 8)
  • BOSS 7.0 Drishti (via Debian 9)
  • BOSS 8.0 Unnati (via Debian 10)

Supported BunsenLabs versions:

  • Hydrogen (via Debian 8)
  • Helium (via Debian 9)

Supported MX Linux versions:

  • MX-17 Horizon (via Debian 9)
  • MX-18 Continuum (via Debian 9)
  • MX-19 Patito Feo (via Debian 10)

Supported Sparky Linux versions:

  • Sparky 4.x Tyche (via Debian 9)
  • Sparky 5.x Nibiru (via Debian 10)

Supported PureOS Linux versions:

  • PureOS 9.0 Amber (via Debian 10)

Supported Astra Linux CE versions:

  • Astra Linux CE 2.12 Orel (via Debian 9)

Installation instructions

Node.js v14.x:

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
sudo apt-get install -y nodejs

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_14.x | bash -
apt-get install -y nodejs

Node.js v12.x:

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_12.x | bash -
apt-get install -y nodejs

Node.js v10.x:

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt-get install -y nodejs

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_10.x | bash -
apt-get install -y nodejs

Node.js LTS (v12.x):

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt-get install -y nodejs

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_lts.x | bash -
apt-get install -y nodejs

Node.js Current (v14.x):

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_current.x | sudo -E bash -
sudo apt-get install -y nodejs

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_current.x | bash -
apt-get install -y nodejs

Optional: install build tools

To compile and install native addons from npm you may also need to install build tools:

# use `sudo` on Ubuntu or run this as root on debian
apt-get install -y build-essential

Manual installation

If you're not a fan of curl <url> | bash -, or are using an unsupported distribution, you can try a manual installation.

These instructions assume sudo is present, however some distributions do not include this command by default, particularly those focused on a minimal environment. In this case, you should install sudo or su to root to run the commands directly.

1. Remove the old PPA if it exists

This step is only required if you previously used Chris Lea's Node.js PPA.

# add-apt-repository may not be present on some Ubuntu releases:
# sudo apt-get install python-software-properties
sudo add-apt-repository -y -r ppa:chris-lea/node.js
sudo rm -f /etc/apt/sources.list.d/chris-lea-node_js-*.list
sudo rm -f /etc/apt/sources.list.d/chris-lea-node_js-*.list.save

2. Add the NodeSource package signing key

curl -sSL https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -
# wget can also be used:
# wget --quiet -O - https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -

3. Add the desired NodeSource repository

# Replace with the branch of Node.js or io.js you want to install: node_6.x, node_8.x, etc...
# The below command will set this correctly, but if lsb_release isn't available, you can set it manually:
# - For Debian distributions: jessie, sid, etc...
# - For Ubuntu distributions: xenial, bionic, etc...
# - For Debian or Ubuntu derived distributions your best option is to use the codename corresponding to the upstream release your distribution is based off. This is an advanced scenario and unsupported if your distribution is not listed as supported per earlier in this README.
DISTRO="$(lsb_release -s -c)"
echo "deb https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee /etc/apt/sources.list.d/nodesource.list
echo "deb-src https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee -a /etc/apt/sources.list.d/nodesource.list

4. Update package lists and install Node.js

sudo apt-get update
sudo apt-get install nodejs

Enterprise Linux based distributions

Available architectures:

NodeSource will continue to maintain the following architectures and may add additional ones in the future.

  • i386 (32-bit) not available for all distros and not available for Node.js 10.x and later
  • x86_64 (64-bit)

Supported Red Hat Enterprise Linux versions:

  • RHEL 7 (64-bit)
  • RHEL 8 (64-bit)

Supported CentOS versions:

  • CentOS 7 (64-bit)
  • CentOS 8 (64-bit)

Supported CloudLinux versions:

  • CloudLinux 6 (32-bit for Node <= 10.x and 64-bit)

Supported Fedora versions:

  • Fedora 30 (64-bit) - available for Node.js 10.16.0 and later
  • Fedora 31 (64-bit) - available for Node.js 10.17.0 and later
  • Fedora 32 (64-bit)

Equivalent versions of Korora Linux should also be supported.

Installation instructions

NOTE: If you are using RHEL 6 or CentOS 6, you might want to read about running Node.js on older distros.

Run as root on RHEL, CentOS, CloudLinux or Fedora:

Node.js v14.x

# As root
curl -sL https://rpm.nodesource.com/setup_14.x | bash -

# No root privileges 
curl -sL https://rpm.nodesource.com/setup_14.x | sudo bash -

Node.js v12.x

# As root
curl -sL https://rpm.nodesource.com/setup_12.x | bash -

# No root privileges 
curl -sL https://rpm.nodesource.com/setup_12.x | sudo bash -

Node.js v10.x

# As root
curl -sL https://rpm.nodesource.com/setup_10.x | bash -

# No root privileges 
curl -sL https://rpm.nodesource.com/setup_10.x | sudo bash -

Node.js LTS (12.x)

# As root
curl -sL https://rpm.nodesource.com/setup_lts.x | bash -

# No root privileges 
curl -sL https://rpm.nodesource.com/setup_lts.x | sudo bash -

Node.js Current (14.x)

# As root
curl -sL https://rpm.nodesource.com/setup_current.x | bash -

# No root privileges 
curl -sL https://rpm.nodesource.com/setup_current.x | sudo bash -

Optional: install build tools

To compile and install native addons from npm you may also need to install build tools:

yum install gcc-c++ make
# or: yum groupinstall 'Development Tools'

Snap packages


Snaps are containerized software packages designed to work across cloud, desktop, and IoT devices. They work natively on most popular Linux distributions and feature automatic transactional updates.

The NodeSource-managed Node.js snap contains the Node.js runtime, along with the two most widely-used package managers, npm and Yarn. They are delivered from the snapcraft store and are automatically built and pushed for each supported Node.js release line. Generally you will have a new version of Node.js automatically running on your computer the same day it is released on nodejs.org.

The Node.js snap can currently be installed on Arch Linux, Debian, Fedora, Linux Mint, Manjaro, OpenEmbedded/Yocto, OpernWrt, Solus, Ubuntu and many other distributions built on top these. NodeSource has not tested the Node.js snap on all of these distributions and feedback is welcome in this repository if you run into problems.

Installation instructions

The snap command ships with Ubuntu, from version 16.04 and later. If you do not have it installed, follow the instructions on snapcraft to install snapd.

Snaps are delivered via channels; for Node.js, the channel names are the major-version number of Node.js. So select a supported Node.js version and install with:

sudo snap install node --classic --channel=8

Substituting 8 for the major version you want to install. Both LTS and Current versions of Node.js are available via snapcraft.

The --classic argument is required here as Node.js needs full access to your system in order to be useful, therefore it needs snaps classic confinement. By default, snaps are much more restricted in their ability to access your disk and network and must request special access from you where they need it. Note that on some Linux distributions, the snap confinement mechanisms are not fully supported so --classic may not be necessary or even supported.

Once installed, the node, npm and yarn commands are available for use and will remain updated for the channel you selected.

Switching channels

You can use the refresh command to switch to a new channel at any time:

sudo snap refresh node --channel=10

Once switched, snapd will update Node.js for the new channel you have selected.

Bleeding-edge Node.js

Users feeling adventurous or interested in testing the latest code from the Node.js core developers can install from the edge channel. This has an element of risk: it is a direct pipeline from the upstream Node.js git repository to the snap store every day and previews the ongoing development work and may include breaking changes slated for the next major version of Node.js. This is only recommend for those users who are willing to participate in testing and bug reporting upstream:

sudo snap install node --classic --channel=edge

Not recommended for production deployments

Due to their auto-updating nature, snaps are not necessarily appropriate for the deployment of your Node.js applications to production. NodeSource recommends a stable and integration-tested deployment pipeline for production applications such as the .deb or .rpm distributions outlined above. However, snaps are an excellent way to keep developer machines updated and allow for trivial and convenient switching between Node.js versions.

Advanced usage

The snap man page, or Canonicals advanced snap usage tutorial contains details of advanced snapd functionality.


To test an installation is working (and that the setup scripts are working!) use:

curl -sL https://deb.nodesource.com/test | bash -


Q: How do I use this repo when behind a proxy?

A: Please take a look at issue #9

Q: How do I pin to specific versions of Node.js?

A: Please take a look at issue #33

Q: I upgraded to a new major version of Node.js using the scripts, but the old version is still being installed, what is going on?

A: You probably need to clear out your package manager's cache. Take a look at issue #191

Q: I'm trying to install Node.js on CentOS 5 / RHEL 5 and it is failing, why?

A: Due to the limitations of the compiler toolchain on EL 5 and its end of general support, we no longer support. See issue #190

Q: I'm seeing Your distribution, identified as.i686or.i386, is not currently supported, why?

A: Node.js 4.x and newer require a 64bit os for rpms. See issue #268

Q: Why have certain versions of platforms/releases stopped receiving updates to Node.js?

A: Unfortunately, newer versions of V8 require a modern compiler toolchain. On some platforms, such as ARM wheezy, that toolchain is not available. See issue #247

Q: Why is my Node.js version newer than the one of the script Ive run?

A: Your package manager is probably installing a newer Node.js version from a different source. See issue #657

Q: What is the current status of IPv6 support?

A: See issue #170

Requested Distributions

We, unfortunately, do not have the resources necessary to support and test the plethora of Linux releases in the wild, so we rely on community members such as yourself to get support on your favorite distributions! This is a list of releases that have been requested by the community. If you are interested in contributing to this project, this would be a great place to start!

Authors and Contributors

Chris Lea GitHub/chrislea Twitter/@chrislea
Rod Vagg GitHub/rvagg Twitter/@rvagg
William Blankenship GitHub/retrohacker Twitter/@retrohack3r
Harry Truong GitHub/harrytruong
Matteo Brunati GitHub/mattbrun
Brian White GitHub/mscdex
Matt Lewandowsky GitHub/lewellyn
Jan-Hendrik Peters GitHub/hennr
Andris Reinman GitHub/andris9
Carvilsi GitHub/carvilsi
Krasimir Trenchev GitHub/Ava7
Phil Helm GitHub/phelma
0xmohit GitHub/0xmohit
jdarling GitHub/jdarling
Prayag Verma GitHub/pra85
Misha Brukman GitHub/mbrukman
Simon Lydell GitHub/lydell
Sebastian Blei GitHub/iamsebastian
Jorge Maldonado Ventura NotABug/jorgesumle
Mayank Metha GitHub/mayankmetha Twitter/@mayankmethad
Adrian Estrada GitHub/edsadr Twitter/@edsadr
Ivn Iguarn GitHub/igsu

Contributions are welcomed from anyone wanting to improve this project!


This material is Copyright (c) NodeSource and licensed under the MIT license. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE.md file for more details.

Supported with love by Chris Lea, Rod Vagg and the NodeSource team

This project is not affiliated with Debian, Ubuntu, Red Hat, CentOS or Fedora.
Ubuntu is a registered trademark of Canonical Ltd.
Debian is a registered trademark owned by Software in the Public Interest, Inc.
Red Hat, CentOS and Fedora are trademarks of Red Hat, Inc.
CloudLinux is a trademark of Cloud Linux, Inc

distributions open issues Ask a question     (View All Issues)
  • over 3 years installing node on older OS versions
  • over 3 years Setup installs End-Of-Life version of Node.js
  • almost 4 years Node Installation on ubuntu 16.04
  • almost 4 years Debian packages should recommend ca-certificates
  • almost 4 years Cannot find module on ubuntuGnome 16.04 with node.js v:4.6.0
  • almost 4 years Unable to install NodeJS 4, 5 or 6 on CentOS 5/6
  • almost 4 years Check for enabled flag repo in scripts
  • almost 4 years The installation script doesn't work correctly on Ubuntu 16.04 LTS. When the user intends to install v6, v4 is actually installed.
  • almost 4 years yum broken on Centos5 when nodesource repo is enabled
  • almost 4 years ipv6 problem
  • almost 4 years CentOS 6.7 not supported
  • almost 4 years REQUEST for support of Node.js v6
  • about 4 years Incorrect version of Node package in Yum repo
  • about 4 years Manual installation instructions for EL / Fedora
  • over 4 years Failed to install on Amazon Cloud desktop system-release-2012.03-3.16.metal.noarch
  • over 4 years Unable to build native addons on Centos 6 with Node 4.3
  • over 4 years https://rpm.nodesource.com/setup_0.12 creates incorrect URL to RPM
  • over 4 years Clean npm installation in pre-install
  • over 4 years RHEL/CentOS 7 repomd.xml timestamp issue
  • about 5 years debian package pinning
  • about 5 years nodejs 0.12 on Fedora 21
  • over 5 years Allow plain HTTP access? (+ apt-cacher-ng HTTPS how-to, + make HTTP mirrors)
  • over 5 years Can you publish nodejs.spec file on github so that others can send pull requests?
  • almost 6 years Install a specific version
distributions open pull requests (View All Pulls)
  • Enforce Root
  • Backward compatibility with RHEL5.1
  • Add elementary OS Loki support
  • Adding contributors table
  • Clean-up manual installation instructions for Debian distributions
  • add v0.10 and v0.12 EOL warning
  • Ensure transfer is complete before execution
  • Kali-rolling support added
  • ElementaryOS 4 - loki support added
  • Add WahaLinux to supported distributions
  • Fix typo in README.md
  • Add Trisquel 8 (flidas) support.
  • Update setup_6.x
  • Add support for DNF, change installation text to reference dnf instead of yum
  • Update setup_7.x
  • Add Oracle Linux
  • Added support for PureOS v8 "green"
  • Added Pardus Alternative
  • Deepin alternative
  • Add: automatic generate Debian script to install Node 8
  • Add: support for SolydXK a distribution based on Debian
  • Add aliases for Devuan Jessie/Ascii/Ceres releases
  • Support for PureOS
  • Remove note about discontinued Linux OS Korora
  • Add Aliyun Linux 2 support
  • README: Add version numbers to elementary OS
  • Mention where you can find RPM package signing key
  • Add support for Ubilinux dolcetto
  • Update _setup.sh - Support for ClearOS
distributions questions on Stackoverflow (View All Questions)
  • Gradle sync failed: Server returned HTTP response code: 522 for URL: https://services.gradle.org/distributions/gradle-2.4-all.zip
  • C++11 random number distributions are not consistent across platforms -- what alternatives are there?
  • Efficiently sampling Hypergeometric Distributions with Large population?
  • How to execute a gradle task before any distributions are built
  • what is select distribution ratio under insert distributions in cassandra stress tool?
  • how to manage multiple Python distributions on one device
  • Python and R(ggplot2): batch histograms to compare the default rates and the distributions of each variable
  • How can I upload both zip and targz distributions to PyPI?
  • Fitting a mixture of lognormal distributions in Python
  • Restart jar with root privileges on most (if not all) Linux distributions
  • Do all Linux distributions implement process capabilities and credentials for security?
  • How do I generate data that have the same mean, standard deviation but very different shapes or distributions in R?
  • What are the interval transforms in pymc3 for uniform distributions?
  • In R topicmodels package, how could we get the topics' distributions over terms?
  • Assign values to records randomly based on given distributions
  • Binary compatibility between Linux distributions
  • Why do the Frechet distributions differ in scipy.stats vs R
  • Draw random numbers from the mixture of uniform distributions
  • random choice, specific distributions, variable applicability
  • Deploying a Qt 5.5.1 C++ application on multiple Linux distributions
  • Difference between nodejs v0.12 and v5.x distributions
  • weak Learners based on distributions : Decision stump
  • Two distributions in with googleVis in R
  • R: How to get a sum of two distributions?
  • How to make a grouped histogram with normal distributions with ggplot?
  • How to strip source from distutils binary distributions?
  • R: How to add normal distributions to overlapping grouped histograms with lattice
  • Java Generator for Poisson and Uniform Distributions?
  • Fitting distributions, goodness of fit, p-value. Is it possible to do this with Scipy (Python)?
  • How to generate vector with different prob. distributions for each element
distributions list of languages used
Other projects in Shell