fix-unused-imports

To fix TS6133 unused imports errors, parse the TypeScript compiler output to extract file paths and identifiers, then remove the unused imports or rename variables with a leading underscore to restore a clean type check.

The best way to remove unused variables causing tsc build failures is to batch process the compiler errors, edit the source files to delete specific named imports, and re-run tsc --noEmit to verify resolution.

Yes, you can automatically clean TypeScript imports after a CI check failure by grouping TS6133 fixes per file, applying the edits to delete entire import lines, and re-running type checks to confirm resolution.

This unused imports fix works with both TypeScript and JavaScript projects, applying declared-but-unused identifier removal during local builds and tsc --noEmit runs when TS6133 errors are reported.

A limitation when auto-removing unused TypeScript imports is that it relies strictly on parsing TS6133 compiler output, meaning it only targets declared-but-unused identifiers and requires re-running type checks to confirm resolution.