Score your next-intl message files on every push and fail the build when a locale regresses.
next-intl throws on a missing message in development but most teams catch only the locales their tests exercise, which is usually the default one. A key missing from de.json sails through CI and surfaces for a real German user instead.
Polylens scans your next-intl message JSON, scores each locale, and lists every missing key, broken ICU argument, malformed plural and stale string, then fails the build when a locale regresses. One curl call, strings stay in your repo.
Locale format: JSON messages (messages/{locale}.json). Point the gate at your messages directory.
A key present in en.json but missing from de.json is invisible until a German user hits it. Polylens lists every gap per locale.
next-intl uses ICU MessageFormat; a translator who drops {count} or {name} breaks the message. Polylens diffs every ICU argument.
A plural block that loses its other branch renders raw syntax. Polylens parses and validates every ICU plural and select.
Reword the source and the old translation stays live with nothing missing. Polylens detects it from scan history.
name: i18n health
on:
pull_request:
paths: ['messages/**']
jobs:
polylens:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: curl -fsSO https://polylens.sh/polylens-ci.mjs
- run: node polylens-ci.mjs ./messages
env:
POLYLENS_TOKEN: ${{ secrets.POLYLENS_TOKEN }}
FAIL_ON: error
NO_REGRESSION: 'true'Add your project token as the POLYLENS_TOKEN repository secret. A failing gate returns HTTP 422, so the build goes red like any other test.
Add one step to your pipeline that posts your locale files to Polylens. The gate returns HTTP 422 when a language regresses, so the build fails like any other test. No SDK, one curl call, and your strings never leave your repo.
Yes. Missing keys are the first of 13 issue classes Polylens detects, alongside broken placeholders, untranslated copy, malformed plurals, and stale strings. Every missing key is listed per language in the dashboard.
No. next-intl renders your translations at runtime; Polylens is the quality gate that scores the locale files before they ship. They sit on opposite ends of the pipeline and work together.
Wire next-intl into a CI gate in ten minutes. Free for one project, no card, strings stay in your repo.