cleaning-project

To remove dead code and unused files, you can run a dry scan to identify orphan files, exported functions never imported, and junk patterns like .DS_Store or .log files, then explicitly confirm which candidates to delete.

The safest way to clean up orphan files after a refactor is to perform a dry run first, which generates a report of unimported files and empty directories, requiring explicit user confirmation before any actual deletion occurs.

You can detect empty directories and junk files before merging by scanning the codebase for common patterns like Thumbs.db, .tmp files, and .log files, which are listed in a report for you to review and approve for removal.

Dead code detection does not require a language server, but it offers optional language-server support to improve accuracy when spotting exported functions and constants that are never imported by other files.

A dry run for codebase cleanup is a preliminary scan that lists all deletion candidates, including dead code and orphan files, preventing accidental deletions by requiring explicit user confirmation before modifying any files.

Yes, you can clean up bloated repositories safely because orphan file detection specifically excludes essential entry points, ensuring that only truly unimported files and empty folders are listed for your confirmation.