// the find
lingodotdev/lingo.dev
Open-source localization engineering tools. Connects to Lingo.dev localization engineering platform for consistent, quality translations.
A localization toolchain for JavaScript/TypeScript projects — CLI, GitHub Action, API, and a build-time React compiler that strips away the usual i18n boilerplate. The hook is a hosted 'localization engine' that persists glossaries and brand voice across requests, sitting on top of whatever LLM you configure. Aimed at JS teams who want automated, continuous translation without managing translation keys by hand.
The lockfile approach (tracking what's already been translated) is genuinely useful — incremental updates mean you're not re-translating unchanged strings on every run. Format support is broad and serious: JSON, YAML, PO, XLIFF, Android XML, Xcode .strings, .xcstrings, Flutter ARB — the demo directory shows they've actually tested these, not just listed them. The React compiler angle is interesting: write plain English in JSX, compiler extracts and generates localized variants at build time, no t() wrappers in the source code. The BYO-LLM option (OpenAI, Anthropic, Ollama, etc.) means you're not locked to their cloud if you don't want to be.
The React compiler is early alpha and only supports Next.js App Router and Vite — no Pages Router, no Remix, no anything else. If your app doesn't fit those two, you're back to the CLI. The hosted 'localization engine' is the default path and the core value-add, but it's a SaaS dependency with no self-hostable equivalent documented — if their service has an outage or their pricing changes, you're stuck. The MCP server targets AI coding assistants for i18n setup help, which sounds useful, but in practice this is just structured docs for Claude/Copilot and not a substitute for actually understanding what next-intl or react-i18next expect from your project structure.