Buzz Node Tools Cache
Buzz keeps a local Node tools cache under its profile to speed up package operations, storing downloaded npm package tarballs, registry metadata JSON, integrity manifests, and temporary extraction leftovers used when it installs or updates bundled developer tools. Over time, interrupted downloads, stale package metadata, or corrupted tarball archives can cause Buzz to reuse bad cache entries instead of fetching fresh ones. Kudu clears only this node-tools cache so Buzz can rebuild it cleanly, while installed node tools, modules, settings, accounts, and passwords stay untouched.
Why clean Buzz Node Tools Cache?
- A corrupted cached npm tarball makes Buzz fail during tool installation or update with repeated extract or integrity errors until the package is downloaded again
- Stale registry metadata JSON can point Buzz at outdated package versions, so update checks say everything is current even though newer tool releases exist
- Interrupted downloads leave partial archives and temp files behind, which can cause installs to hang at fetching or unpacking on every retry
- Mismatched integrity manifests in the cache trigger checksum verification failures, showing users repeated EINTEGRITY-style errors for the same package
- An oversized cache full of old tarballs and metadata wastes AppData disk space and slows package resolution because Buzz scans more stale entries before falling back to the network
- Cache entries created before a registry mirror change or network proxy fix can keep serving bad responses, so Buzz continues to report package fetch failures after connectivity is otherwise fixed
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.