Tech Ventures

How to Delete Node js Completely in 2025

Written by

in

Wait, Why Would You Even Want To Remove Node?

You might love node for quick scripts, big apps, or a fun side-project on the server side.
But maybe a test went sideways, or you kept piling up multiple versions until the machine feels stuffed.
Old configuration files lurk, the npm cache keeps swelling, and a mystery npm err pops up every other build.
So, you whisper: How can I get a clean slate?
That’s what this friendly guide is for.
For a concise, future-proof checklist, you can also glance at this 2025 guide to deleting Node.js completely.

Quick Outline Before We Dig In

  1. Spot every place Node hides
  2. Use the following commands on Windows, macOS, and Linux
  3. Scrub the usr local bin node and its buddies
  4. Tidy the npm cache and global npm packages
  5. Check the path variable and other environment variables
  6. Verify it’s completely erased
  7. Learn safer ways like node version manager for next time

Let me explain each bit in bite-size steps.

Little Reminder: Back Up First

Copy your project folders to a home directory backup drive or cloud.
You’ll feel better.

Section 1 – Spot What’s Installed On Your System

Open a command prompt or type terminal window and run the following line:

node -v

If you see any node v readout, there is an installed node copy hiding.
Also run:

npm -v

If there is an npm version, great, we know node.js and npm are still living on the system.

Section 2 – Windows Clean Uninstall, Step By Step

Heading: Use Apps & Features First

  1. Hit Start → Settings → Apps.
  2. Scroll to Node.js.
  3. Tap uninstall and press enter twice.
    That runs the official installer in reverse.

If the default uninstaller leaves traces, consult the community-vetted answers in this Stack Overflow thread on completely removing Node.js from Windows for extra cleanup steps.

Heading: Sweep Program Folders

Even after the wizard, many leftover files stick.
Open File Explorer and delete these:

  • C:Program Filesnodejs
  • C:Program Filesnodejsnode_modules

Yes, get rid of every node gyp, temp build, and other files.

Heading: Clear User AppData

%AppData%npm
%AppData%npm-cache

Trash those folders.
You just freed megabytes of npm cache.

Heading: Touch The Registry (Carefully)

Use regedit, search Node.js.
Remove associated files and NodePath entries from:

  • HKEY_CURRENT_USERSoftwareNode.js
  • HKEY_LOCAL_MACHINESOFTWARENode.js

Now the Windows piece is successfully removed.
Need a cross-platform reference that covers Windows, macOS, and Linux in one place? Check out this complete Node.js uninstallation walkthrough for all operating systems.

Section 3 – macOS: The Brew Route

Heading: Did You Use Homebrew?

If you ran brew install node in the past, open Terminal and:

brew doctor
brew uninstall node

That single line “run brew uninstall node” triggers Homebrew’s remover and kills most node files.

Heading: Extra Brew Cleanup

brew cleanup

Run twice for luck.
Still see node v?
Move on.

Heading: Manual Folder Hunt

Use the following commands:

sudo rm -rf /usr/local/bin/node
sudo rm -rf /usr/local/bin/npm
sudo rm -rf /usr/local/bin/npx
sudo rm -rf /usr/local/lib/node
sudo rm -rf /usr/local/include/node
sudo rm -rf /usr/local/share/man/man1/node.1
sudo rm -rf /usr/local/share/man/man1/npm.1
sudo rm -rf /usr/local/share/doc/node
sudo rm -rf /usr/local/share/systemtap/tapset/node.stp

Notice how many sudo rm calls target:

  • usr local bin
  • usr local lib
  • usr local share
  • usr local share man
  • local share man man1

Delete them all.
That’s a clean uninstall for macOS. If you’d prefer a mac-specific set of fast steps, this focused article on removing Node.js from macOS in 2025 walks through the same process with screenshots.

Section 4 – Linux: Apt, Snap, And Friends

Heading: Debian / Ubuntu Apt Method

If you used apt:

sudo apt get remove --purge nodejs npm
sudo apt get autoremove
sudo apt get clean

Those apt get sweeps uninstall nodejs core packages and purges configuration files.

For stubborn packages on Ubuntu that refuse to vanish, the solutions gathered in this Stack Overflow post about completely uninstalling Node.js, npm, and Node in Ubuntu often resolve the issue.

Heading: Snap Method

sudo snap remove node --purge

Again, we purge for a completely remove action.

Heading: Hunt Down Leftovers

Run the following commands:

sudo rm -rf /usr/local/lib/node_modules
sudo rm -rf /usr/local/lib/node
sudo rm -rf /usr/local/bin/node
sudo rm -rf /usr/local/bin/npm
sudo rm -rf /usr/local/share/man/man1/node.1
sudo rm -rf /usr/local/share/man/man1/npm.1
sudo rm -rf /usr/local/include/node
sudo rm -rf /usr/local/lib/dtrace/node.d

See how we touched usr local lib node_modules and local lib dtrace?
Those hide deep leftover files.

Section 5 – One-Liner For The Brave

Some devs ask for a script.
Here’s a short yet fierce bash snippet:

for p in 
/usr/local/lib/node_modules 
/usr/local/lib/node 
/usr/local/include/node 
/usr/local/bin/node 
/usr/local/bin/npm 
/usr/local/bin/npx 
/usr/local/share/man/man1/node.1 
/usr/local/share/man/man1/npm.1; do
  sudo rm -rf $p;
done

Run it, and node is completely uninstall node in seconds.

Section 6 – Fixing Environment Variables

After you manually remove all those paths, open .bashrc, .zshrc, or .profile.
Look for any export PATH=.../node parts.
Delete them.
That tidies the environment variables so builds won’t search ghost bins.

Section 7 – Verify It’s Gone

Run:

node -v
npm -v
which node
which npm

They should return nothing.
Congratulations, you completely remove Node from the system.

Section 8 – Reinstall Node The Smart Way

You may want to reinstall node but safer.
Try install nvm:

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

Now you can manage node versions with:

nvm install 20
nvm use 20

No more multiple installations clutter.
Plus, switching versions is a breeze.
For a wider look at how modern engineering teams streamline Node deployment and versioning at scale, you can browse the latest reports on TechVentures.

Section 9 – Common Questions

Question: I Used The Official Installer On Mac, Not Brew. Now What?

Delete:

  • /usr/local/lib/node
  • /usr/local/bin/node
  • /usr/local/bin/npm
  • /usr/local/share/man/man1/node.1

Those are the core usr local bin and usr local lib targets.

Question: My global npm packages Are Still Hanging Around!

Remove them with:

npm ls -g --depth=0
sudo npm rm -g <package>

Or nuke the folder:

sudo rm -rf /usr/local/lib/node_modules

Question: What About node gyp Cache?

sudo rm -rf ~/.cache/node-gyp

Simple.

Section 10 – Special Cases

Heading: Enterprise Servers

On the server side, use your ops tool (

More posts