missing-file: missing locale file

error — fails the build

A locale file that exists for the source language has no counterpart for a target language — the namespace is entirely untranslated for that locale.

What triggers it

locales/
  en/  common.json  checkout.json
  fr/  common.json               // checkout.json missing

Fixed

locales/
  en/  common.json  checkout.json
  fr/  common.json  checkout.json

Why it matters

A missing namespace file usually means a whole feature ships untranslated for that market, and the per-key checks never even get to run.

How to fix it

Create the file — shipi18n translate generates it from the source namespace in one run.

How to silence it

Not silenceable per-key; if a namespace is deliberately not translated for a locale, exclude it from your check invocation's directory layout.

Check for this in CI

npx @shipi18n/cli check ./locales -s en
# SARIF for inline PR annotations:
npx @shipi18n/cli check ./locales -s en -r sarif -o shipi18n.sarif

The structural checks need no API key. Findings of this rule link back to this page from the SARIF helpUri.

Related rules

• invalid-json — broken JSON in a translation file
• missing-key — missing translation keys