Dustoff – CLI to find and remove JavaScript/TS build artifacts
Cleans up JS build artifacts, but tree-shaking and bundlers already solve this.

Regex instead of AST parsing: 12ms dependency tree for 500 files versus 50ms+ for competitors.
TypeScript/JavaScript developers, build tool maintainers, monorepo teams
madge · dependency-tree · TypeScript Compiler API
Given a changed file, it tells you every file that depends on it. This is useful for things like: - selective test runs - cache invalidation - incremental builds - impact analysis when refactoring
The main focus is speed. Instead of parsing ASTs, importree scans files using carefully tuned regex, which makes it extremely fast even on large projects.
I built it while working on tooling where I needed to quickly determine which parts of a codebase were affected by a change.
Hope you'll find it as useful as I do: https://github.com/alexgrozav/importree
Happy to answer any questions!
Cleans up JS build artifacts, but tree-shaking and bundlers already solve this.
20x faster knip—performance leap is real, but dependency linters are crowded and knip already solved this.
Decision table minimizer with QM algorithm, but audience is narrow domain experts.
ESLint for system design: catch architecture violations in CI before code review becomes bottleneck.
AI agents navigate your Java UI natively without hallucinating state bugs.
Dependency graph persists across AI sessions; Claude never rescans the same files twice.