Like many developers, I recently found my NVMe SSD running out of space, only to discover nearly 80 GB consumed by stray dev artifacts: old Rust target/ debug builds,abandoned Python virtual environments (.venv), dead node_modules, and orphaned AI/ML model weights scattered across nested folders.
Existing tools like npkill are great, but they are limited to Node.js and can be slow across deeply nested monorepos. Running raw rm -rf carries serious risk of deleting uncommitted code or active branches.
To solve this, I built nodewipe — an open-source, surgical dev-cache cleaner written in Rust.
The Hard Engineering Challenges
Building a tool that scans and deletes across 39+ ecosystems surfaced several fascinating systems-level problems.
1. Apparent Size vs. Physical Block Allocation (st_blocks * 512)
Most CLI tools report file size via standard stat.len(). On modern filesystems (APFS, ext4, Btrfs), this is often wildly inaccurate due to sparse files, small cluster tail packing, and filesystem metadata overhead.
A folder containing 20,000 tiny files might have an apparent size of 1 MB, but physically occupy 80 MB of 4 KB disk clusters. On Unix, nodewipe calculates st_blocks * 512 to measure the true physical block footprint allocated by the filesystem rather than just apparent byte length.
2. Zero-Cost Instant Backups via CoW Reflinks
Before deleting large folders, having an undo mechanism is crucial. Traditional backups require compressing to .tar.gz, which introduces heavy I/O blocking.
On filesystems that support Copy-on-Write (clonefile on APFS for macOS, and FICLONE on Btrfs/XFS for Linux), nodewipe probes the mount point and creates an instantaneous,0-byte cost reflink snapshot. Restoring is instant and non-destructive. If CoW is unavailable, it gracefully falls back to the OS Trash or .tar.gz.
3. Rayon Work-Stealing & Path Interning
Traversing 500k+ files across nested monorepos without ballooning heap memory or exhausting file descriptors required optimization:
- Parallel directory traversal powered by Rayon work-stealing thread pools.
- An internal
PathInternerthat deduplicates common parent directory string prefixes across parallel worker threads, reducing memory footprint by over 60%.
4. Safety Markers & Git Awareness
Generic directory names like build/ or dist/ are not always disposable. Nodewipe uses a multi-tiered marker system: a candidate directory is only flagged if its parent or interior contains definitive proof of belonging to that toolchain (e.g., verifying Cargo.toml, package.json, pyproject.toml, or virtualenv binaries). It also queries local Git status to warn if a project has uncommitted changes.
Triple Interface: CLI, Interactive TUI, and GUI
Whether you prefer keyboard-driven terminal workflows or visual dashboards, nodewipe supports three modes:
Interactive TUI (Ratatui): Full keyboard navigation, real-time live size calculations, multi-select, and instant search/filtering.
Headless CLI: Scriptable flags (
--dry-run,--older-than 30d,--min-size 500MB,--types node,rust,python).Native Desktop GUI: Lightweight desktop app built with Tauri v2.
Quick Install
nodewipe is distributed across all major package managers:
# Cargo (crates.io) cargo install nodewipe # macOS (Homebrew) brew install KADHIRAVANEG/nodewipe/nodewipe # Windows (Scoop) scoop bucket add nodewipe https://github.com/KADHIRAVANEG/scoop-nodewipe scoop install nodewipe # Arch Linux (AUR) yay -S nodewipe # NPM (standalone wrapper) npm install -g @joker53/nodewipe Open Source & Contributing
nodewipe is 100% free and open-source under the MIT license.
• GitHub Repository: KADHIRAVANEG/nodewipe https://github.com/KADHIRAVANEG/nodewipe
• Architecture Deep Dive on Medium: Read the full article https://medium.com/@kadhiravanegk/reclaiming-80-gb-of-invisible-dev-bloat-building-nodewipe-in-rust-f0ab0f56024b?sharedUserId=kadhiravanegk
If you find it useful or it saves space on your development machine, please consider giving the repository a star on GitHub! Feedback, bug reports, and rule suggestions are warmly welcome!

