i18n-check

To find hardcoded strings for internationalization, you can scan your React or Vue source directories to identify static user-visible text and automatically generate corresponding i18n translation keys.

The best way to extract translation keys from static strings is to use an automated scanner that detects text in JS, TS, JSX, and Vue files, then generates consistent keys and updates your locale files.

Yes, you can automatically replace hardcoded text with i18n function calls in Angular or React by scanning files, generating translation paths, and substituting the identified strings with the appropriate function calls.

Yes, i18n extraction works with TypeScript and Vue files by scanning JS, TS, JSX, TSX, and Vue file types to detect typical i18n library usage and extract user-visible strings accordingly.

To update locale files like en.json when adding new translation keys, the extraction process automatically generates the keys from found strings and appends them to your existing locale configuration.