Is this useful for App Router projects?

Yes. The workflow is file-based and works with JSON locale files used by App Router or Pages Router apps.

Can I validate next-intl files in CI?

Yes. The @json-translate/check CLI compares translated JSON files against the source locale for missing keys and placeholder drift.

Developer JSON translation

Translate next-intl JSON locale files

Next.js localization files can grow quickly across pages, components, and namespaces. Keep the JSON shape stable while producing draft translations faster.

Translate next-intl JSON Compare limits

Works with nested namespace-style locale files

Preserves route, component, and UI message key paths

Fits a CI workflow with the free @json-translate/check CLI

A safer JSON translation flow

Translate one namespace at a time

Start with a page or shared namespace so reviews stay small and practical.

Protect runtime variables

Keep placeholders, product names, and route-like strings unchanged where the app expects exact values.

Run a production build smoke test

Check localized routes in the built Next.js app before merging translated files.