SiftMac
Who it’s for · Updated 21 November 2026

What fills a web developer’s Mac, from node_modules to Docker

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What fills a web developer’s Mac
  2. What’s safe to clear, and what to keep
  3. How SiftMac helps a web developer
  4. A cleanup routine for a web developer’s Mac
  5. Questions

1. What fills a web developer’s Mac

Node keeps a full copy of each project’s dependencies inside the project, and every tool around it keeps a cache of its own. The usual list:

WhatWhere it livesComes back?More
node_modules in old projectsInside each projectYes, from the lockfile with npm ci, pnpm install, yarn or bun installnode_modules
Framework build caches.next, .nuxt, .svelte-kit, .turbo, .parcel-cache, .angularYes, on the next build or dev runNext.js .next
npm’s cache~/.npmYesnpm cache
pnpm, Yarn and Bun cachespnpm’s store (pnpm store path prints it), ~/Library/Caches/Yarn, ~/.bunYespnpm, Yarn, Bun
Browsers for tests~/Library/Caches/ms-playwright, ~/Library/Caches/CypressYes, installed again by the test runner—
Node versions~/.nvm/versions/node, or your version manager’s folderOnly by installing them again—
Docker images, build cache and containersDocker.raw, inside Docker Desktop’s containerImages pull again; volumes don’tDocker.raw
Browser cachesChrome, Firefox and Safari cache foldersYesChrome, Firefox, Safari
Editor caches and installed updatesVS Code’s and Cursor’s folders, ~/Library/Caches/<app ID>.ShipItYesVS Code, Cursor
Electron build downloads~/Library/Caches/electron, ~/Library/Caches/electron-builderYes—

Measure the shared caches, biggest last:

du -sh ~/.npm ~/.bun ~/.nvm ~/Library/Caches/Yarn ~/Library/Caches/pnpm ~/Library/Caches/ms-playwright ~/Library/Caches/Cypress ~/Library/Caches/electron 2>/dev/null | sort -h

Then every node_modules under your projects folder (change ~/code), and what Docker could give back:

find ~/code -name node_modules -type d -prune -exec du -sh {} + 2>/dev/null | sort -h | tail -20
docker system df

2. What’s safe to clear, and what to keep

Clear with each tool’s command

Docker: free space from inside

Docker Desktop keeps every image, container, volume and build layer in one disk image, so deleting files in Finder can’t shrink it. docker system prune removes stopped containers, networks no container uses, dangling images and unused build cache; -a also removes every image no container uses, and volumes stay unless you add --volumes. docker builder prune clears the build cache on its own. To cap the disk image, lower the disk usage limit in Docker Desktop’s Resources settings, where you can also move the image to another drive.

Keep

3. How SiftMac helps a web developer

SiftMac’s developer files list node_modules and the caches of Next.js, Nuxt, SvelteKit, Parcel, Turborepo and Angular only where a package.json sits beside them, and only in projects you haven’t changed for 1, 3 or 6 months. A monorepo counts as one project: if any package in it changed recently, none of its folders is listed.

npm’s ~/.npm, ~/.bun and ~/.nvm live outside ~/Library/Caches, and SiftMac doesn’t clean them. The space map shows their size, so you can clear them with the commands above.

4. A cleanup routine for a web developer’s Mac

  1. Push your work and list the projects you’re in this month.
  2. Run docker system df, then prune what’s reclaimable; keep volumes.
  3. In old projects, delete node_modules and framework caches, or run npx npkill to pick them from a list.
  4. Clear package caches: npm cache verify (or npm cache clean --force), pnpm store prune, yarn cache clean, bun pm cache rm.
  5. Prune test browsers with Playwright’s and Cypress’s own commands.
  6. Remove Node versions you don’t use.
  7. Open your current project, install, and start the dev server once to check it still builds.

Questions

Is it safe to delete node_modules?

Yes, in any project with a lockfile. npm ci (or pnpm install, yarn, bun install) recreates it with the same versions. Without a lockfile you may get newer versions than before, so commit one first.

Why didn’t Docker.raw get smaller when I deleted images?

Docker.raw is a sparse disk image: Finder shows its maximum size, while du -h shows what it really uses. Free space with docker system prune or docker image prune -a, and lower the disk usage limit in Docker Desktop if you want a hard cap.

Does npm cache clean slow anything down?

Only the next installs, which download packages again instead of copying them from the cache. Nothing in your projects changes.

How SiftMac handles it. SiftMac lists node_modules and framework build caches only in projects you haven’t changed for months and only next to a package.json, and frees Docker space with Docker’s own prune commands when you turn that on, never touching volumes.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works