Can this replace FormatJS extraction?

No. Keep using FormatJS extraction for source messages, then use JSON Translate for draft locale output.

Why mention placeholder validation?

FormatJS messages often contain ICU arguments. Those tokens need to survive exactly for runtime formatting.

Developer JSON translation

Translate FormatJS JSON files safely

FormatJS catalogs need careful handling because a small placeholder mistake can break runtime formatting. Keep IDs stable and review ICU-heavy strings first.

Translate FormatJS JSON Compare limits

Designed for message catalog JSON workflows

Protects the structure around IDs and message values

Pairs well with a CLI validation step before merge

A safer JSON translation flow

Start with extracted source messages

Use the source catalog produced by your FormatJS extraction flow.

Translate draft message values

Keep message IDs unchanged while translating the human-readable copy.

Validate placeholders

Use app tests and @json-translate/check to catch missing or changed placeholder tokens before release.