Tools: How to Install Node.js on Ubuntu

By Brian Boucheron, Anish Singh Walia and Manikandan Kurup Node.js is a JavaScript runtime for server-side programming. It allows developers to create scalable backend functionality using JavaScript, a language many are already familiar with from browser-based web development. In this guide, we will show you three different ways to install Node.js on an Ubuntu server: For many users, using apt with the default repo will be sufficient. If you need specific newer or legacy versions of Node, you should use the PPA repository. If you are actively developing Node applications and need to switch between node versions frequently, choose the nvm method. Note:
This article will walk you through installing Node.js on an Ubuntu server. If you want a one-click way to deploy a Node application to a live server, take a look at DigitalOcean App Platform. To follow this guide, you will need an Ubuntu server. Before you begin, you should have a non-root user account with sudo privileges set up on your system. You can learn how to do this by following the Ubuntu initial server setup tutorial. Ubuntu 24.04 contains a version of Node.js in its default repositories that can be used to provide a consistent experience across multiple systems. At the time of writing, the version in the repositories is v24.x. This will not be the latest version, but it is stable and sufficient for quick experimentation. To get this version, you can use the apt package manager. Refresh your local package index first: Then install Node.js: Check that the install was successful by querying node for its version number: Note: Your output may differ depending on when you install. If the package in the repositories suits your needs, this is all you need to do to get set up with Node.js. In most cases, you’ll also want npm, the Node.js package manager. On some Ubuntu versions, npm is installed automatically with nodejs. If it is missing, you can install it separately with apt: This allows you to install modules and packages to use with Node.js. At this point, you have successfully installed Node.js and npm using apt and the default Ubuntu software repositories. The next section will show how to use an alternate repository to install different versions of Node.js. To install a different version of Node.js, you can use a PPA (personal package archive) maintained by NodeSource. These PPAs have more versions of Node.js available than the official Ubuntu repositories. Node.js v24 and v25 are available as of the time of writing. First, install the PPA to get access to its packages. From your home directory, use curl to retrieve the installation script for your preferred version, making sure to replace 25.x with your preferred version string (if different): Refer to the NodeSource documentation for more information on the available versions. Inspect the contents of the downloaded script with nano or your preferred text editor: When you are satisfied that the script is safe to run, exit your editor. Then run the script with sudo: The PPA will be added to your configuration and your local package cache will be updated automatically. You can now install the Node.js package in the same way you did in the previous section: Verify that you’ve installed the new version by running node with the -v version flag: The NodeSource nodejs package contains both the node binary and npm, so you don’t need to install npm separately. At this point, you have successfully installed Node.js and npm using apt and the NodeSource PPA. The next section will show how to use the Node Version Manager to install and manage multiple versions of Node.js. Another way of installing Node.js that is particularly flexible is to use nvm, the Node Version Manager. This piece of software allows you to install and maintain many independent versions of Node.js, and their associated Node packages, at the same time. To install NVM on your Ubuntu machine, visit the project’s GitHub page. Copy the curl command from the README file that displays on the main page. This will get you the most recent version of the installation script. Before piping the command through to bash, it is always a good idea to audit the script to make sure it isn’t doing anything you don’t agree with. You can do that by removing the | bash segment at the end of the curl command: Review the script and make sure you are comfortable with the changes it is making. When you are satisfied, run the command again with | bash appended at the end. The URL you use will change depending on the latest version of nvm, but as of right now, the script can be downloaded and executed with the following: This will install the nvm script to your user account. To use it, you must first source your .bashrc file: Now, you can ask NVM which versions of Node are available: It’s a very long list. You can install a version of Node by writing in any of the release versions listed. For instance, to get version v24.13.0, you can run: You can view the different versions you have installed by listing them: This shows the currently active version on the first line (-> v22.22.0), followed by some named aliases and the versions that those aliases point to. Note: If you also have a version of Node.js installed through apt, you may receive a system entry here. You can always activate the system-installed version of Node using nvm use system. Additionally, there are aliases for the various long-term support (or LTS) releases of Node: You can install a release based on these aliases as well. For instance, to install the latest long-term support version, krypton, run the following: You can switch between installed versions with nvm use: You can verify that the install was successful using the same technique from the other sections: The correct version of Node is installed on your machine as expected. A compatible version of npm is also available. You can uninstall Node.js using apt or nvm, depending on how it was installed. To remove the version from the system repositories, use apt remove: By default, apt remove retains any local configuration files that were created since installation. If you don’t want to save the configuration files for later use, use apt purge: To uninstall a version of Node.js that you installed using nvm, first determine whether it is the current active version: If the version you are targeting is not the current active version, you can run: This command will uninstall the selected version of Node.js. If the version you would like to remove is the current active version, you first need to deactivate nvm to enable your changes: Now you can uninstall the current version using the uninstall command used previously. This removes all files associated with the targeted version of Node.js. When starting a new project, installing Node.js is a crucial step. Node.js allows developers to run JavaScript on the server-side, making it a popular choice for web applications. For example, if you’re building a real-time chat application, you might want to use Node.js with a framework like Express.js to handle incoming requests and send responses. To illustrate this, let’s consider a scenario where you’re building a simple chat application using Node.js and Express.js. You want to create a server that listens for incoming messages and broadcasts them to all connected clients. Here’s a simple example of how you might structure your server-side code using Node.js and Express.js: This example demonstrates how Node.js can be used to create a server that handles real-time communication between clients. To install Node.js for app development, you can use the methods described earlier in this tutorial. For instance, you can use apt to install Node.js from the Ubuntu repository or use nvm to install a specific version of Node.js. Here’s an example command to install Node.js using apt: Alternatively, you can use nvm to install a specific version of Node.js. First, install nvm if you haven’t already, then use the following command to install a specific version of Node.js: Replace <version> with the version number you want to install. Node.js is widely used for setting up backend projects due to its event-driven, non-blocking I/O model. This makes it lightweight and efficient for handling multiple concurrent connections. For example, if you’re building a RESTful API, Node.js can be used to create the server-side logic, handle database interactions, and return data to the client. When setting up a backend project, you might want to use a framework like Express.js or Koa.js to simplify the process. These frameworks provide a structure for organizing your code and handling HTTP requests and responses. Managing multiple Node.js versions is essential when working on different projects that require different versions of Node.js. NVM (Node Version Manager) is a popular tool for managing multiple Node.js versions on a single machine. For example, let’s say you’re working on two projects: one that requires Node.js version 22.x and another that requires Node.js version 24.x. With NVM, you can easily switch between these versions without affecting the system’s default Node.js version. To switch between Node.js versions using NVM, you can use the following command: Replace <version> with the version number you want to use. This command will switch your Node.js version to the specified one, allowing you to work on your project without affecting other projects that require different versions. Permission issues with global installs occur when you try to install a package globally using npm without having the necessary permissions. This is because global packages are installed in a system directory that requires root access. Why it occurs: This error occurs because npm tries to write to a directory that requires root access, but the user running npm does not have those permissions. How to fix it: To fix this issue, you can use one of the following methods: NVM not found after install occurs when you install NVM but do not source the NVM script in your shell profile. Why it occurs: This error occurs because NVM is not added to your system’s PATH after installation. The NVM script needs to be sourced in your shell profile to make NVM available. How to fix it: To fix this issue, you need to add the following line to your shell profile file (e.g., ~/.bashrc or ~/.zshrc): Then, restart your terminal or run source ~/.nvm/nvm.sh to apply the changes. Conflicts between apt and NVM-installed versions occur when you have Node.js installed using both apt and NVM. This can cause issues with package management and version conflicts. Why it occurs: This error occurs because both apt and NVM install Node.js in different locations, leading to conflicts between the two installations. How to fix it: To fix this issue, you should remove the Node.js installation from apt and use NVM as the primary method for managing Node.js versions. Here’s how to do it: The best way to install Node.js on Ubuntu is to use a package manager like NVM (Node Version Manager) or a NodeSource PPA. These methods provide more flexibility and allow for easy version management. To check your Node.js version, run the command node -v in your terminal. This will display the version of Node.js installed on your system. Yes, you can install multiple versions of Node.js using a package manager like NVM. NVM allows you to install, manage, and switch between different versions of Node.js easily. NVM (Node Version Manager) is a tool that allows you to easily install, manage, and switch between different versions of Node.js on your system. You should use NVM because it provides a convenient way to manage multiple Node.js versions, which is particularly useful for developers who need to work with different projects that require different Node.js versions. To uninstall Node.js completely, you need to remove all Node.js packages and dependencies. If you installed Node.js using apt, you can uninstall it by running sudo apt purge nodejs. If you used NVM, you can uninstall Node.js by running nvm uninstall node. Most Ubuntu installations do not come with Node.js preinstalled. You need to install it manually using a package manager or by downloading the binaries. To update Node.js on Ubuntu, you can use the package manager you used to install it. If you used apt, you can update Node.js by running sudo apt update && sudo apt full-upgrade. If you used NVM, you can update Node.js by running nvm install node --latest. There are several ways to set up Node.js on your Ubuntu server, each with its own advantages. Whether you choose to use the packaged version, nvm, or a NodeSource PPA, the key is to select the method that best fits your project’s requirements. To further explore Node.js and its applications, we recommend checking out the following tutorials and resources: By following these guides, you’ll be well on your way to mastering Node.js and deploying your applications efficiently. Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases. Learn more about our products Node.js is a JavaScript platform for general-purpose programming that allows users to build network applications quickly. By leveraging JavaScript on both the front and backend, Node.js makes development more consistent and integrated. To get your development environment configured so you can start building Node.js applications. select the tutorial for your platform. Browse Series: 9 tutorials Senior Technical Writer at DigitalOcean I help Businesses scale with AI x SEO x (authentic) Content that revives traffic and keeps leads flowing | 3,000,000+ Average monthly readers on Medium | Sr Technical Writer @ DigitalOcean | Ex-Cloud Consultant @ AMEX | Ex-Site Reliability Engineer(DevOps)@Nutanix With over 6 years of experience in tech publishing, Mani has edited and published more than 75 books covering a wide range of data science topics. Known for his strong attention to detail and technical knowledge, Mani specializes in creating clear, concise, and easy-to-understand content tailored for developers. This textbox defaults to using Markdown to format your answer. You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link! I really appreciated the 3 options you gave us. I wonder though…
I went with NVM and copied the code snippets to install it. Should I have used sudo with these commands. It appears that nvm was installed but only for my sudo user. I’m hoping (and guessing) this won’t be an issue. Thanks you! If you want the nvm node version to be the default, ie stay set after reboot run this.
$ nvm alias default <your version> When following “Option 3 — Installing Node Using the Node Version Manager” you will be unable to “sudo npm”. This can be fixed by running this command: If you go with option 1 or 2, you will probably face permission error issues. In this case, make sure to configure npm to use a different directory. Thanks Brian. This doc is very clear and complete and helped me a great deal. If you’re using Option 2, you need to run sudo apt update after you’ve added the PPA to your configuration, otherwise you’ll get an error message about being Unable to locate package node.js… In the version of this tutorial for ubuntu 18.04, there are instructions for installing the build essentials package, but not here. This is not required for this version? If you’re using a non root user and having issues like this:
“E: Failed to fetch http://mirrors.digitalocean.com/ubuntu focal InRelease”
Try the command “sudo apt-get update”.
If you have problem also with this command then you have to change the fetch link that gives you the error. If you type “ls” you should see a “sources.list” file. We need to edit that. Type: “vim sources.list” Activate editor by pressing “i” then move to every link that has “mirrors.digitalocean.com” and change it to “archive.ubuntu.com”. When you finish, press “esc” then “:w !sudo tee % > /dev/null”.
File should be saved now. Try installing nodejs now. Should work fine. node -v
node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27’ not found (required by node) Please complete your information! Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation. Full documentation for every DigitalOcean product. The Wave has everything you need to know about building a business, from raising funding to marketing your product. Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter. New accounts only. By submitting your email you agree to our Privacy Policy Scale up as you grow — whether you're running one virtual machine or ten thousand. Sign up and get $200 in credit for your first 60 days with DigitalOcean.* *This promotional offer applies to new accounts only.