Hi HN, We built Dustoff to solve a small but annoying problem that kept appearing across development environments.

Hi HN, We built Dustoff to solve a small but annoying problem that kept appearing across development environments. Modern JavaScript and TypeScript projects generate a lot of build artifacts such as node_modules, .next, dist, .cache, coverage and others. When you work across many repositories these directories accumulate quickly and can consume a lot of disk space. Dustoff scans a directory, detects common build artifacts, and lets you interactively browse, sort and safely remove them. The CLI allows you to: - sort artifacts by size or age - search and filter directories - group artifacts by project - select multiple entries quickly using keyboard navigation - delete them with confirmation You can run it instantly without installing anything: npx dustoff Curious to hear feedback from other developers and whether people run into similar cleanup issues across projects.

Posted by max-roma on Mar 4, 2026, 12:11 PM

Tags

• hackernews (Other)

Related issues

• The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
• (My comment is about detached houses).
• The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
• > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
• Why is there no comparison with FLUX 3 Image?
• > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...