sync-translations

Synchronizing translation JSON files across locales ensures consistent keys by comparing each locale against a base file like de.json to detect missing or orphaned keys. This process validates structural drift, preserves interpolation placeholders, and updates all locale files to mirror the base.

Finding missing translation keys in next-intl locale files involves comparing every locale against a reference file such as de.json to list keys that are absent or orphaned. This detection scans messages and identifies structural drift in nesting or namespace shapes between locale files without automatically restructuring them.

Generating a complete locale file for a newly added locale in next-intl is supported by creating a full set of translation messages matching the base locale. This ensures all keys are present, ICU syntax and placeholders are preserved, and the new file mirrors the structure of the reference locale.

The synchronization approach works with Next.js projects using next-intl where code references use useTranslations, getTranslations, and t(...) patterns under the src/ directory. It scans these patterns to validate that translation message files across locales remain consistent and aligned with the base locale.

ICU syntax and interpolation placeholders are preserved when syncing locale files across locales. The synchronization process ensures that placeholders and JSON formatting remain intact while adding missing keys to all locales, preventing broken translations caused by mismatched variable references.