DEV Community

Discussion on: How do teams actually handle localization during development, CI, or even docs?

Collapse
 
kwun_ng_a66e33742de275cb7 profile image
Kwun Ng

This is exactly what i18n-validate does. Standalone CLI for CI pipelines:

# In CI (GitHub Actions, GitLab CI, etc.):
npx @i18n-agent/i18n-validate --base src/locales/en.json --targets src/locales/*.json --min-coverage 90 --fail-on-error
Enter fullscreen mode Exit fullscreen mode

It checks: missing keys, extra/stale keys, broken placeholders, CLDR plural completeness, parse errors. Outputs terminal, JSON, or JUnit XML.

For pre-translation testing, add i18n-pseudo to generate pseudo-localized files that catch layout/hardcoding issues before real translation.

Both support 32 formats (JSON, YAML, PO, XLIFF, ARB, strings.xml...). Zero-config auto-detect.

Install: npm install -g @i18n-agent/i18n-validate @i18n-agent/i18n-pseudo