Bun Cache

Why clean Bun Cache?

• A partially downloaded or truncated package tarball in Bun’s install cache can trigger checksum or extraction errors during bun install, which shows up as failed dependency installs for packages that previously worked
• Old cached versions of packages you no longer use keep consuming disk space in ~/.bun/install/cache, and users usually notice Bun taking several gigabytes even after deleting old projects
• Stale registry metadata or cached package artifacts can cause Bun to keep reusing an unexpected package build, leading to confusing cases where a clean install still behaves differently from CI or another machine
• Interrupted installs can leave broken cache entries behind, causing repeated retries, fetch failures, or installs that hang on the same dependency until the cache is cleared
• Corrupted extracted package contents in the cache can surface as missing files, postinstall script failures, or modules that cannot be resolved even though the package name appears in the lockfile
• Shared cache reuse across many projects means one bad cached artifact can break multiple bun install runs, so the symptom often appears as unrelated repositories failing on the same dependency
• Cleaning the cache forces Bun to redownload fresh package tarballs and metadata, which often fixes persistent install errors without deleting project source code, node_modules settings, or login credentials

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.