Frameworks
Your i18n library, your files, one sync line.
A setup page per library: where its locale files live, how it reads them, and the one line that keeps them in sync from your pipeline. Pick your framework, then your library.
Angular
Both read the same JSON in src/assets/i18n. Transloco is the library Mergua was built alongside; ngx-translate works with it as it is, no migration needed.
Angular + Transloco
First-classManage Angular and Transloco translations on git-style branches. Nested JSON in src/assets/i18n, reviewed before it merges, synced from your CI pipeline in one line.
Set up TranslocoAngular + ngx-translate
SupportedManage Angular and ngx-translate translations on git-style branches. The src/assets/i18n JSON your loader already reads, synced from CI in one line — no migration needed.
Set up ngx-translateReact
i18next reads nested JSON, react-intl looks every message up by a flat id — and that is the whole difference on Mergua's side: one --format flag in the sync line.
React + i18next
SupportedManage React and i18next translations on git-style branches. Your src/locales JSON files, synced from CI in one line — react-intl and its flat message ids included.
Set up i18nextReact + react-intl
SupportedManage React and react-intl translations on git-style branches. FormatJS message ids in src/lang kept flat, ICU plurals checked, synced from CI in one line.
Set up react-intlNext.js
Vue
Svelte
Flutter
Your library is not on the list?
Mergua reads nested JSON, flat JSON and ARB, whichever library loads them. Point the sync script at the folder and name the format — each page above is that one line worked out for a stack, not a list of what is allowed. The guides cover the files themselves.
Bring the locale folder you already have.
Branch your translations, review them, and sync them from your pipeline. Free to start.
Create your account