i18n-extract

To find hardcoded strings for internationalization in a React codebase, this Skill scans your TypeScript files to identify and extract user-facing text from JSX, attributes, and template literals. It generates a structured inventory of all translatable strings to streamline your workflow.

Yes, you can configure file scanning for string extraction using glob patterns. This allows you to target specific directories within your TypeScript project and exclude irrelevant files from the internationalization inventory process.

Yes, the tool detects and flags potential false positives during string extraction. It classifies identified hardcoded text by domain and priority, helping you distinguish actual user-facing strings from internal logic before proceeding with translation.

The best way to inventory translatable text in a TypeScript application is to automate scanning with a tool that categorizes extracted strings by domain. This generates a comprehensive, structured report ready for translation workflows without manual searching.

A limitation of automated string extraction for localization is the potential for false positives in complex codebases. While configurable rules help refine detection, you must still review the generated structured report to ensure all flagged template literals and attributes require translation.