Check locale files from your terminal or CI — and retranslate just the keys that fail. The fastest way to start.
npm install -D @shipi18n/cli
# or run it without installing
npx @shipi18n/cli --helpSet your own LLM key in the environment. It is read at translation time and never written to disk or sent anywhere except your provider:
# .env — never commit this
ANTHROPIC_API_KEY=your-key-hereUse OPENAI_API_KEY instead if you pass --provider openai.
npx @shipi18n/cli translate locales/en.json -t es,fr,deexport ANTHROPIC_API_KEY=your-key-here
npx @shipi18n/cli translate locales/en.json -t es,fr,de
# writes locales/es.json, locales/fr.json, locales/de.json# Existing translations are reused; only new or empty keys hit the model.
npx @shipi18n/cli translate locales/en.json -t es,fr --incrementalexport OPENAI_API_KEY=your-key-here
npx @shipi18n/cli translate locales/en.json -t ja,ko -p openaiExport ANTHROPIC_API_KEY (or OPENAI_API_KEY with -p openai) in the shell that runs the command. The CLI does not read .env files automatically — use dotenv or your shell.
The CLI warns when a placeholder present in the source is absent from a translation. Re-run that language; if it repeats, the string is usually ambiguous — add context to the key name.
Use npx @shipi18n/cli, or add it as a devDependency and call it through an npm script.
Need help? Read the docs