tl-knip

You can find and remove unused dependencies in a TypeScript monorepo by running a configuration-first dead-code analysis that auto-detects framework plugins and resolves barrel files. This reliably identifies unused exports and dependencies across multi-project codebases.

Automating dead-code cleanup in a CI pipeline involves running a configuration-first analysis that surfaces unused files, dependencies, and exports. The workflow reduces false positives and provides agent guidance for reliable removal across JavaScript and TypeScript projects.

Yes, Knip works with barrel files and path aliases by handling them natively during the unused export analysis. This ensures that re-exported modules and aliased imports are correctly traced, preventing false positives during dependency cleanup.

You can clean up unused exports across multi-project codebases while preserving your public API by utilizing a configuration-first workflow. This approach surfaces hints and manages resources carefully, ensuring essential public exports remain untouched during dead-code removal.

False positives in dead-code analysis often occur when framework plugins, path aliases, or barrel files are not properly resolved. A configuration-first workflow with auto-detected plugins and alias resolution mitigates these issues by accurately tracing dependency usage.

You can configure Knip to recognize custom assets and scripts by enabling optional references and resources. This on-demand guidance allows the analysis to account for non-standard dependencies, ensuring they are not flagged as unused files during the cleanup process.