Complete Guide to Uninstalling Node.js, npm and node in Ubuntu

Introduction

During software development, there are situations where complete removal of Node.js and its related components becomes necessary, such as when resolving version conflicts, freeing up system space, or reconfiguring development environments. Node.js installed via package manager in Ubuntu systems may leave behind configuration files, cache data, and globally installed packages, making simple removal commands insufficient for thorough cleanup. Based on community-verified best practices, this article provides a complete uninstallation solution to ensure Node.js, npm, and all related files are completely removed.

Core Steps for Node.js Uninstallation

In Ubuntu systems, if Node.js was installed using the sudo apt-get install node command, the complete uninstallation process requires multiple steps. First, remove the main packages using the package manager:

sudo apt-get remove nodejs
sudo apt-get remove npm

These commands remove Node.js and npm packages from the system package manager but may retain configuration files. To ensure thorough cleanup, it's recommended to check and remove any Node.js-related entries from the software sources list. Navigate to the /etc/apt/sources.list.d directory, locate and delete any Node.js-related source files, then update the package cache:

sudo apt-get update

Cleaning Residual Files and Directories

After package manager removal, configuration files and cache data may still exist in user directories. These files include globally installed npm packages, Node.js module caches, and configuration information. Check and delete the following directories:

rm -rf ~/.npm
rm -rf ~/.node-gyp

Additionally, check other potential locations in the system. Use the which command to locate node and npm executable files:

which node
which nodejs
which npm

If these commands return any paths, it indicates residual executable files remain in the system that need manual deletion. Common residual locations include directories like /usr/local/bin/, /usr/local/lib/node_modules/, and /opt/local/bin/.

Verifying Uninstallation Results

After completing all removal steps, verify that Node.js has been completely removed from the system. Execute the following commands for verification:

node -v
npm -v

If the system returns "command not found" or similar error messages, it indicates successful removal of Node.js. Additionally, run the which command again to confirm no executable files remain:

which node
which npm

You can also check if related packages have been completely removed from the package manager:

dpkg -l | grep node
dpkg -l | grep npm

These commands should return no results, indicating all Node.js-related packages have been removed.

Reinstalling Node.js Using NVM

To avoid similar uninstallation issues in the future, it's recommended to use Node Version Manager (NVM) for installing and managing Node.js. NVM allows users to install multiple Node.js versions in user space without sudo privileges and enables easy switching between different versions. The command to install NVM is:

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

After installation, restart the terminal or execute the following commands to load NVM:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"

After verifying successful NVM installation, use NVM to install the latest version of Node.js:

nvm install node
nvm install --lts

NVM automatically installs the corresponding version of npm. Verify the installation after completion:

node --version
npm -v

Configuring npm Global Installation Path

After installing Node.js using NVM, configure npm to install global packages in the user directory to avoid permission issues. First, create a global installation directory:

mkdir ~/.npm-global

Then configure npm to use this directory:

npm config set prefix '~/.npm-global'

Finally, add the global installation directory to the PATH environment variable. Edit the ~/.profile file and add the following line:

export PATH="$HOME/.npm-global/bin:$PATH"

Execute the following command to make the configuration effective:

source ~/.profile

Common Issues and Solutions

During the uninstallation and reinstallation process, some common issues may arise. If Node.js versions are still detectable after uninstallation, it may be due to multiple installation sources in the system. Check all possible installation locations, including installations via source compilation, other package managers, or manual installations.

Another common issue is permission conflicts. Node.js installed via system package manager typically requires sudo privileges for global package installation, which may cause file permission混乱. Installing via NVM completely avoids this issue since all files are installed in the user directory.

If module compatibility issues occur after reinstallation, consider using NVM to install specific Node.js versions or check the Node.js version requirements specified in the project's package.json file.

Conclusion

Completely uninstalling Node.js, npm, and related components from Ubuntu systems requires a systematic approach. By removing packages via package manager, cleaning configuration files and residual directories, and verifying removal results, users can ensure thorough removal of all related components. Reinstalling Node.js using NVM not only simplifies version management but also avoids permission issues, providing a more stable and flexible environment for development work. Following the complete process provided in this article enables users to safely and efficiently complete Node.js uninstallation and reconfiguration.