Apps
Bun Cache
Bun stores downloaded package tarballs and extracted package cache entries under ~/.bun/install/cache so repeated bun install operations can reuse them instead of fetching every dependency again. That cache speeds up installs, but over time it can accumulate outdated package archives, interrupted download remnants, and corrupted metadata that lead to checksum mismatches or repeated resolution failures. Kudu removes Bun's downloaded package cache contents while leaving your projects, lockfiles, global packages, settings, accounts, and passwords untouched.
Why clean Bun Cache?
- A truncated tarball from an interrupted download can make bun install fail with extraction or integrity errors even though the registry package itself is fine
- Stale cached package contents can cause Bun to keep reusing an older archive, so a dependency update appears ignored until the cache is cleared
- Corrupted cache metadata leads to repeated fetch retries and long install times, which shows up as installs hanging on the same package over and over
- Hundreds of cached package versions and tarballs accumulate under ~/.bun/install/cache, consuming significant disk space long after those dependencies are no longer used
- Registry-side republished or fixed package archives can conflict with an older local cached copy, producing checksum mismatch messages during install
- Cache entries left behind from failed installs can cause inconsistent behavior between projects, where one machine installs cleanly but another keeps failing on the same dependency
What gets cleaned
Cache paths Kudu targets
Windows
~/.bun/install/cache |
macOS
~/.bun/install/cache |
Linux
~/.bun/install/cache |
Frequently asked
Common questions about Bun Cache
Related cleaners
Free & open source
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.