Buzz Node Tools Cache
Buzz stores a local Node tools cache under its profile to speed up package resolution and downloads, keeping npm-style tarball archives, package metadata responses, integrity index files, and extracted temporary fetch data so it does not need to re-download every dependency for each tool action. When that cache becomes stale or partially corrupted, Buzz can keep reusing bad registry metadata or damaged package archives, leading to repeated install and update failures. Kudu clears only Buzz's node-tools cache contents so package downloads can be fetched cleanly again, while installed node tools, modules, accounts, settings, and passwords remain untouched.
Why clean Buzz Node Tools Cache?
- Corrupted cached npm tarballs cause repeatable install or update failures in Buzz, often showing checksum, integrity, or unexpected end of archive errors
- Stale package metadata makes Buzz think an older tool version is current, so updates do not appear or the app keeps resolving the wrong dependency version
- Interrupted downloads leave partial fetch data in the cache, which can trigger endless retry loops or installs that fail at the same percentage every time
- Outdated registry response cache can point Buzz at removed or superseded package versions, leading to 404 errors even though the package exists upstream
- A bloated cache of old tarballs and metadata can consume hundreds of megabytes over time, which users notice as growing AppData disk usage with no change to installed tools
- Mismatched cached integrity data and package archives can make Buzz repeatedly re-verify and re-download dependencies, causing unusually slow tool setup compared with a clean fetch
Cache paths Kudu targets
Windows
%AppData%/Buzz/node-tools/cache |
Common questions about Buzz Node Tools 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.