Find and fill missing react-i18next keys
A German common.json that fell behind the English one does not fail the build. i18next falls back to English or prints the key, and nobody notices until a user does. Below, one command finds the gaps and another fills them.
The example project
A small react-i18next project: the English source and a German file that fell behind. The commands below ran on exactly these files.
{
"header": {
"greeting": "Hi, {{name}}!",
"signOut": "Sign out"
},
"cart": {
"items_one": "{{count}} item in your cart",
"items_other": "{{count}} items in your cart",
"checkout": "Go to checkout",
"terms": "By paying you accept the <1>terms</1>."
}
}
{
"header": {
"greeting": "Hallo, {{name}}!",
"signOut": "Abmelden"
},
"cart": {
"items_one": "{{count}} Artikel im Warenkorb",
"checkout": "Zur Kasse",
"terms": "Mit der Zahlung akzeptieren Sie die AGB."
}
}
1. Find what is missing
kaeris check compares each translation with the source file. It runs offline with no key or account, and exits with code 1 when it finds a problem, so a CI job can stop on it.
$ npx kaeris check --source public/locales/en/common.json --langs de
✗ de: 1 missing key(s): cart.items_other
✗ de: 2 translation fault(s):
cart.terms: lost inline tag </1>
cart.terms: lost inline tag <1>
✗ 1 missing key, 2 translation faults
2. Translate only the missing keys
--only-new sends only the keys the German file lacks and merges them in. Lines already in the file stay as they are, broken ones included. The command is in the Python package: pip install kaeris.
$ kaeris translate public/locales/en/common.json --langs de --only-new
→ no key: free demo limits 10,000 chars per file, 8 languages per run, get a key: kaeris.dev/developer
→ de: 1 new key(s) to translate
→ Run: openai/gpt-6-luna · Free · 1/1 languages · 1 strings · 4.4s
28 charged
✓ Translation QA: no placeholder loss, no overflow risks
✓ de: merged 1 key(s) → public/locales/de/common.json
→ 5 key(s) already exist in de but nothing in kaeris.lock vouches for them, so they were left alone AND left unlocked. If the source changed after those files were made, those edits are NOT translated. Re-run once with --no-only-new to rebuild them, or with --assume-current if the files are known to match.
{
"header": {
"greeting": "Hallo, {{name}}!",
"signOut": "Abmelden"
},
"cart": {
"items_one": "{{count}} Artikel im Warenkorb",
"checkout": "Zur Kasse",
"terms": "Mit der Zahlung akzeptieren Sie die AGB.",
"items_other": "{{count}} Artikel in Ihrem Warenkorb"
}
}
3. Check again
The missing keys are filled. What is left was broken before this run: fix those lines by hand, or translate the whole file again with --no-only-new.
$ npx kaeris check --source public/locales/en/common.json --langs de
✗ de: 2 translation fault(s):
cart.terms: lost inline tag </1>
cart.terms: lost inline tag <1>
✗ 2 translation faults
Run on 2 November 2026 on the free tier, without a key: npx kaeris 0.2.42 for the check, kaeris 0.2.42 from PyPI for the translation. Output as printed, except that progress lines and the local folder path are left out.
What kaeris check catches in react-i18next
Missing keys, plural suffixes included
A key the source has and the translation lacks, such as
cart.items_otherwhen only_onewas copied.Lost or renamed
{{name}}Interpolations are compared line by line.
{{Name}}in place of{{name}}is reported as one lost and one invented.<Trans>tagsNumbered tags such as
<1>terms</1>must come back, or the link inside the sentence disappears.Not checked yet
Plural keys a language needs and English does not have, such as Polish
_fewand_many.
What it costs
kaeris checkis freeIt runs on your machine: no key, no account, no limit.
Translation is free to start
Without a key: 10,000 characters per file, 300,000 a day, up to 8 languages per run. A free key raises this to 50,000 characters per file and 1.5M a month. Volume counts characters once per target language.
Beyond the free tier
Lifetime is $79 once and runs on your own OpenRouter key, so the model is paid separately. Pro is $19 a month or $190 a year for 12M characters a month. Pricing
Questions
Does it find keys used in code but missing from the files?
No. kaeris check compares locale files with each other. Run an extractor such as i18next-cli first so the English file has every key; the check takes it from there.
Which folder layouts work?
locales/en/common.json next to locales/de/common.json, or en.json next to de.json. The check looks where translate writes.
Can it run in CI?
Yes. npx kaeris check exits with code 1 when it finds a problem. Recipes: GitHub Actions, GitLab CI, pre-commit.
Keep going
Check reference · CLI reference · Free check in the browser · Translate in the browser
Other stacks: next-intl · vue-i18n · Flutter · iOS · Android