Is it safe to delete the npm cache (~/.npm/_cacache)?

What is it?

npm keeps every package tarball and registry response it downloads in a content-addressed cache, ~/.npm/_cacache, so later installs can skip the network. It is shared by all projects, is never trimmed automatically, and typically grows to one to several gigabytes.

What happens if you delete it?

npm downloads packages again the next time a project needs them, so the next installs are slower and need a connection. Your projects’ node_modules folders are separate and keep working.

How to remove it properly

Run npm cache clean --force in Terminal, npm’s own command, which deletes the cache permanently. If you only suspect corruption, npm cache verify checks the cache and removes unneeded data without emptying it.

Use the tool’s official command: npm cache clean --force

How MoreRoom helps

MoreRoom recognises this item, shows its real size and when it was last used, and labels it “Safe to remove”. In the free version you can move it to the Trash in one click, with Undo; Pro collects every safe item at once.

When the tool is installed, MoreRoom runs its official command for you (npm cache clean --force) instead of deleting files — and tells you that this step can’t be undone.