Buzz Node Tools Cache
Buzz stores a local Node tools cache under its profile to speed up package resolution and installation, keeping downloaded npm tarballs, package metadata indexes, integrity manifests, and temporary extraction artifacts so it does not need to fetch the same tool payloads repeatedly. When that cache becomes outdated or inconsistent with the current registry state, Buzz can reuse bad metadata or corrupted archives during installs and updates. Kudu clears only this node-tools cache so Buzz rebuilds fresh package downloads and metadata, while installed node tools, modules, settings, accounts, and passwords stay intact.
Why clean Buzz Node Tools Cache?
- Corrupted cached npm tarballs cause repeat install failures with checksum or extraction errors when Buzz tries to provision a tool from a bad local archive
- Stale package metadata makes Buzz resolve an older version than the registry currently serves, so updates appear to do nothing or the wrong tool version keeps reinstalling
- Interrupted downloads leave partial archives and temp extraction files behind, leading to endless retry loops or tools that fail immediately after installation
- Old integrity manifests cached for previous package contents can trigger mismatch warnings, making Buzz report package verification errors until fresh metadata is fetched
- A bloated node-tools cache grows with obsolete tarballs and index data, consuming large amounts of AppData disk space and slowing cache scans before installs
- Registry-side package deprecations or republished metadata can conflict with Buzz's local cache, causing missing dependency errors or unexpected version resolution during setup
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.