knip-cleanup

To find unused files in a Next.js project, run a static analysis dry-run report to identify dead code across files, exports, and dependencies. This process safely targets large codebases and ensures no accidental deletions occur before explicit approval.

You cannot automatically remove unused dependencies without explicit confirmation. The cleanup process enforces safe-by-default behavior through dry-run analysis, applying deletions only after you review the report and grant explicit approval.

The best way to safely clean up dead code is using a dry-run reporting mechanism that identifies unused files, exports, and dependencies. This allows you to review potential deletions and reclaim unused code without breaking builds.

Static analysis for dead code works directly with Next.js and TypeScript projects. It detects unused files, exports, and dependencies, providing starter configurations and guided cleanup to maintain large applications safely.

To generate a knip configuration for dead code analysis, you can use a starter generation tool that creates a knip.json file. This provides the necessary setup to begin guided cleanup and identify unused code in your project.