b2b-backend-refactor-clean

To safely remove unused code in a TypeScript monorepo, use automated analysis tools like knip, depcheck, and ts-prune to detect dead exports and dependencies, then enforce a full test suite run before any deletion to preserve behavior.

Finding unused dependencies and dead exports in a backend project is best done by running knip, depcheck, and ts-prune to surface unused modules and verify candidate removals against the full test suite.

Yes, you can use knip and ts-prune together to refactor a multi-module backend by cross-referencing their results to accurately identify and prune unused TypeScript exports and dependencies.

Yes, you need to run the full test suite before deleting dead code because the refactor-clean process enforces it to verify that removing identified unused dependencies and exports does not break existing runtime behavior.

Pruning unused TypeScript code requires multiple analysis tools because knip, depcheck, and ts-prune each detect different types of dead code and unused dependencies across various modules, ensuring comprehensive and safe removal.

Depcheck focuses on detecting unused dependencies but does not identify unused TypeScript exports, so you must combine it with ts-prune and knip and run the full test suite to safely prune code without breaking behavior.