find-unextracted-i18n

You can audit i18n coverage by scanning TypeScript and JavaScript source files to pinpoint hardcoded strings not yet extracted into translation keys, outputting only the file paths requiring localization.

Yes, you can audit localization coverage on specific changesets identified by Git commit hashes or ranges, allowing you to verify that changed files have properly internationalized user-facing copy before merging.

No, the hardcoded string audit operates strictly as a read-only process. It scans TypeScript and JavaScript files to identify untranslated text and output file paths without making any modifications, ensuring safety during review.

The best way to audit i18n coverage across a directory is to scan it for TypeScript and JavaScript files, filtering by extension while excluding test files and specific directories, yielding a list of files containing hardcoded text needing translation key extraction.

Limitations include filtering files strictly by extension and excluding specific directories and test files. It scans only TypeScript and JavaScript source files, adhering to detection rules similar to standard i18n key extraction processes.