ts-unused-exports vs Rev-dep
ts-unused-exports reports unused exported symbols in a TypeScript project. rev-dep covers that with unusedExportsDetection and a lot more.
At a glance​
| ts-unused-exports | Rev-dep | |
|---|---|---|
| Primary focus | unused exports | dependency hygiene + architecture |
| Runtime | Node | Go - single parallel pass (faster) |
| Unused exports | yes | yes |
| Completely-unused files | yes (--findCompletelyUnusedFiles) | yes (orphan files) |
| Autofix | no | yes (config run --fix) |
| Dependencies / cycles / boundaries | no | yes |
Where rev-dep is stronger​
- One tool for unused exports, orphan files, dependencies, cycles, and architecture rules.
- Autofix removes dead exports.
- Speed on large repos, and monorepo-aware whole-graph context.
Where ts-unused-exports may still fit​
It's a focused, scriptable CLI with fine-grained flags (--allowUnusedTypes, --ignoreLocallyUsed, inline // ts-unused-exports:disable-next-line). rev-dep maps most of these to config options, but if you've built tooling around its exact CLI output, factor that in.
Which should you choose?​
For ongoing, repo-wide hygiene, rev-dep. For a minimal, single-purpose unused-export check, ts-unused-exports stays viable.