Question 1

Does react-i18next work with i18n Coverage?

Accepted Answer

Yes. The Lokali GitHub Action reads react-i18next's default public/locales/{lng}/{namespace}.json layout, posts a per-language PR comment with a missing-keys table, and opens a Coverage delta PR when new keys land.

Question 2

Which i18next file layouts does the action scan?

Accepted Answer

The Action scans core i18next layouts including locales/**/*.json and src/i18n/**/*.json, then flags any language whose keys are missing compared to the source namespace.

Question 3

Does the action support Vue with vue-i18n?

Accepted Answer

Yes. The Action covers Vue's flat-locale layout (locales/*.json and src/locales/*.json), detects missing keys per locale, and supports both Vue 3 composables and the Options API.

Question 4

Does the action support Angular with @angular/localize / ngx-translate?

Accepted Answer

Yes. The Action detects Angular's src/locale/messages.{lang}.xlf (and messages.{lang}.json) sibling layout, scans component $localize template tags inside the PR diff, and reports missing entries plus ICU plural/select drift per locale.

Question 5

What does the action check for next-intl?

Accepted Answer

The Action detects the messages/{lang}.json and locales/{lang}/*.json layouts used by next-intl's App Router setup, including nested namespace files, and reports coverage gaps per language.

Question 6

How does the action scan react-intl translation files?

Accepted Answer

The Action scans the translation file shapes react-intl apps typically commit alongside their defineMessages calls, including src/locales/{lang}.json and translations/{lang}/*.json.

Question 7

Does the action support FormatJS ICU MessageFormat?

Accepted Answer

Yes. The Action matches the canonical FormatJS layout — one file per locale at the repo root or under translations/ — and flags any missing ICU MessageFormat entries.

i18n coverage for the frameworks you already use

Install the i18n Coverage GitHub Action