wipzy

JavaScript: node_modules and package caches

Every project keeps its own node_modules, and each package manager keeps a cache of everything it ever downloaded. These guides show how to measure both, clear them with the tool's own command, and get them back.

Three node_modules folders in a list: two marked Safe with npm ci and pnpm install, one marked Your call because the project was worked on 6 days ago

JavaScript

How to delete all node_modules folders on a Mac

Find every node_modules folder on your Mac, see what each one weighs, and delete the idle ones with one find command. Every one comes back with npm ci.

, 5 min read

The path ~/.npm/_cacache above the commands npm cache verify and npm cache clean --force, with the npm cache marked Safe

JavaScript

How to clear the npm cache, and when you should

The npm cache lives in ~/.npm/_cacache. See its size with du, clean it with npm cache clean --force, and learn why npm cache verify is usually the better call.

, 5 min read

The command pnpm store prune above three rows: the pnpm store marked Your call, the Yarn cache and the Bun cache marked Safe

JavaScript

Clear the pnpm store and the Yarn and Bun caches

pnpm store prune, yarn cache clean and bun pm cache rm, explained: where each cache lives on a Mac, how to see its size, what goes, and how it comes back.

, 5 min read

The folder ms-playwright with three browser builds, chromium, firefox and webkit, marked Your call with the command npx playwright install

JavaScript

Remove old Playwright and Puppeteer browsers

Playwright, Puppeteer and Cypress each download their own browsers into a cache folder. See how much they take, remove old versions, and reinstall in one line.

, 5 min read

New guides arrive in the Atom feed of the Wipzy blog. To see the app these guides lead to, watch Wipzy clean a Mac in 47 seconds, read how the four risk levels work, or see what is free and what Pro adds.