Bun Cache

• A truncated tarball left behind after a cancelled or interrupted install can make later bun install runs fail with integrity or extraction errors for the same package
• Republished or replaced package contents on a registry mirror can leave Bun reusing stale cached artifacts, so you keep seeing an old dependency version even after forcing a reinstall
• Corrupted cached package metadata can send Bun back into repeated resolve or fetch attempts, which shows up as installs hanging on the same dependency or redownloading packages unexpectedly
• An oversized ~/.bun/install/cache from many projects and version changes can consume multiple gigabytes, leaving obvious low-disk-space warnings and slower package cleanup on the system
• Mixed cache contents from switching registries, scopes, or authentication contexts can cause fetch mismatches where one machine keeps failing on a package that installs normally elsewhere
• Old extracted package artifacts can mask whether a dependency problem is in the lockfile or only in the local cache, so clearing the cache is a clean way to rule out local package corruption
• Large package caches on SSD-constrained development machines increase disk churn during dependency updates, and users often notice longer backup times or slower searches through the home directory

Common questions about Bun Cache

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.