node_modules, .venv and build folders across your projects

What it looks for

A folder only counts when the file that makes it next to it, so a stray build folder without a known build system is never reported:

• node_modules next to package.json, and .parcel-cache;
• .next, .nuxt, .svelte-kit, .angular and .turbo next to their framework's config;
• .venv next to pyproject.toml, uv.lock or requirements.txt;
• Pods next to a Podfile, and .build next to Package.swift;
• target next to Cargo.toml or pom.xml;
• build and .gradle next to Gradle files, and build and .dart_tool next to pubspec.yaml.

Which projects

Only the folders you add under Project folders in Settings › General, each either a project or a folder of projects, up to four levels deep. Worktrees are left to the agent worktrees view. One row per project and kind, from 20 MB up.

A project is stale when none of its manifests, lockfiles or git state changed within your staleness window, 30 days unless you change it. Stale projects are marked and rated lower; active ones are still listed, rated by what you would lose.

Getting it back

Cleaning moves the folder to the Trash, and the preview names the command that restores it. For node_modules that is npm install, pnpm install, yarn install or bun install, chosen from the project's lockfile. Build output comes back with the next build.

More of what DevSweeper finds

• Xcode
• Simulators
• Agent worktrees
• Caches and Docker