flutter_reap 0.1.1

Find and delete Flutter build artifacts you stopped using months ago. Dry run by default.

flutter_reap

Free up disk space from old Flutter projects. Finds the build/, .dart_tool/, ios/Pods and android/.gradle directories you stopped using months ago — plus Xcode DerivedData, Gradle caches, and fvm SDKs no project references — and deletes them only after you say which to keep. Dry run by default.

Think npkill, but for Flutter: one command across every project on the machine, instead of flutter clean one repo at a time.

Works on macOS, Linux and Windows.

Is this what you're looking for?

Yes, if you're asking any of these:

• How do I free up disk space taken by Flutter builds?
• How do I run flutter clean on all my projects at once?
• What's using tens of gigabytes in ~/Library/Developer/Xcode/DerivedData?
• Which of my Flutter projects still have build folders I don't need?
• Which fvm SDK versions can I safely delete?
• Is there an npkill for Flutter / Dart?

Not what you want if: you need to clean a single project you're actively working in (flutter clean is right there), or you want to clear the shared pub cache (dart pub cache clean — this tool deliberately never touches it).

Install

dart pub global activate flutter_reap

This puts flutter_reap in ~/.pub-cache/bin (%LOCALAPPDATA%\Pub\Cache\bin on Windows). Add that to your PATH if it isn't already. Anyone with Flutter installed already has the Dart toolchain, so there is nothing else to install.

Use

flutter_reap ~              # scan home, show everything, delete nothing
flutter_reap ~ --days 90    # only projects untouched for 90+ days
flutter_reap ~ --delete     # list, then choose what to keep

Illustrative output — not a measured figure, just the shape of it:

  1. 1840M    214d  ~/AndroidStudioProjects/old-client-app
  2.  920M    131d  ~/AndroidStudioProjects/side-project
  3.   12M      3d  ~/AndroidStudioProjects/current-work
  4. 14204M          ~/Library/Developer/Xcode/DerivedData
  5.  3100M          ~/.gradle/caches
--- 5 dirs, 20076M reclaimable
(dry run - pass --delete to remove)

Options

-d, --days <n>     only projects idle n+ days (default 0)
    --delete       enter the delete flow (default is a dry run)
    --no-caches    skip machine-wide caches
    --json         machine-readable output, implies a dry run
-y, --yes          delete without review; requires --days
-h, --help
-v, --version

What it looks at

Per project: build/, .dart_tool/, ios/Pods, macos/Pods, android/.gradle.

Machine-wide caches and fvm SDKs are only included when the scan root is your home directory — narrowing the root to a subfolder of projects can't accidentally touch them:

• Xcode DerivedData and the CocoaPods cache (macOS)
• ~/.gradle/caches and ~/.android/cache (macOS, Linux and Windows)

If you use fvm, it also flags SDK versions no project references — roughly 1–3 GB each. Silent if you don't use fvm.

Why not just flutter clean

flutter clean is one project at a time, and you have to remember which projects exist. dart pub cache clean is all-or-nothing. Neither knows that you last touched old-client-app in March.

How it decides something is stale

The last commit date for git projects, falling back to pubspec.yaml's modification time for projects that aren't git repos — never the build directory's own timestamp, which resets on every build and would make a two-year-dead project look freshly touched.

Safety

• Dry run unless you pass --delete. Even then, nothing is removed until you answer the keep which? prompt: an empty answer deletes everything listed, k cancels, and anything that doesn't parse also cancels rather than guessing.
• --yes skips that prompt, but is rejected unless you also pass --days. Even then it only ever deletes project artifacts (build/, .dart_tool/, Pods, .gradle) — machine-wide caches and fvm SDKs are never deleted unattended, no matter what --days you pass. Reviewing those requires the interactive prompt.
• Deletion is refused for any directory whose final path segment isn't a known generated name (build, .dart_tool, Pods, .gradle, caches, cache, DerivedData, CocoaPods, or an fvm SDK version directory), and for anything sitting directly under a filesystem root. A bug in path handling cannot reach lib/, pubspec.yaml, or your source.
• ~/.pub-cache is never in the list of machine-wide caches this tool considers on any platform (see "What it looks at" above) — it's shared across every project and slow to refetch. Use dart pub cache clean if you really want it gone.
• dart test covers all of the above, including that a directory which isn't a known generated name is never deleted, and that declining the prompt deletes nothing.

Platform support

Tested in CI on Linux, macOS and Windows.

License

MIT.