Hey Product Hunt, I built Glot because I got tired of shipping broken translations. I run [Noveble](https://www.noveble.com), a novel writing platform that supports 19 languages. At that scale, things slip through constantly. A developer hardcodes a button label in English. A translation key gets used in code but never added to the locale file. A language file accumulates stale keys from features that were removed months ago. Users in Japan see random English strings and file bug reports. I wanted one command that catches all of this before it hits production. `npx glot check` scans your Next.js codebase and reports: - Hardcoded text in JSX that should use translation functions - Translation keys referenced in code but missing from locale files - Values in non-primary locales that are identical to the primary (likely untranslated) - Orphan keys that exist in replica locales but not in the primary If you have a large existing codebase, `npx glot baseline` suppresses current warnings so you can add it to CI immediately and chip away at the backlog over time. It also ships with an MCP server, so if you use Claude Code, Cursor, or similar tools, they can detect and fix i18n issues directly. Built for next-intl, which is what most Next.js projects use for i18n these days. Two commands to try it: ``` npm install -D glotctl npx glot check ``` Curious what i18n headaches others are dealing with. Happy to answer any questions.

Glot

ESLint for your translations, built for next-intl

ESLint for your translations, built for next-intl