JavaScript tooling has a blind spot: codebase-wide questions
summary
Large TypeScript/JavaScript repos need a deterministic codebase truth layer, not just file-level linters; a Rust-native tool called Fallow builds an import/export graph to find dead exports and unused package.json deps, detect duplication and cyclomatic complexity (McCabe warns risk above 10), flag high crap score hotspots, and enforce architectural boundaries. It also ships a runtime beacon to collect production function usage so agents can turn “looks safe” into “delete with confidence,” and it integrates into CI and agent workflows.
AI-written summary · about
chapters (9)
- 0:00AI and deterministic tooling
- 3:41Linters' limitations
- 6:09Introducing Fellow
- 8:39Unused code and duplication
- 10:26Complexity measurement
- 12:55Architectural boundaries
- 13:57Fellow with AI and CI
- 15:01Production monitoring
- 17:08Conclusion
