i18n-validate

To check i18n JSON files for missing translations, validate locale paths against a reference language to detect incomplete keys. This ensures translation completeness by identifying any untranslated strings across your supported languages.

Detect orphaned keys and placeholder mismatches in localization files by running consistency validation against a reference language. This flags unused keys and incorrect variable usage, ensuring format integrity and preventing runtime errors.

The best way to validate JSON syntax errors in locale files before merging is to run automated format integrity checks. This verifies that all internationalization files are valid JSON, preventing parsing failures in your application.

You can enforce glossary alignment and length violations during translation consistency validation by applying configurable validation rules. This checks translated strings against defined glossaries and length limits to maintain quality.

Yes, i18n validation works with a custom reference language and specific locale paths. You can configure the validation rules to operate on specified languages, ensuring all translations match your chosen baseline.

Your internationalization validation reports orphaned keys because those keys exist in your translation files but are missing from the reference language. Removing these unused keys ensures structural consistency across all locales.