LingoLint

ESLint for app translations. Catch i18n bugs in CI.

2 followers

ESLint for app translations. Catch i18n bugs in CI.

2 followers

ESLint for app translations. Catch missing keys, broken placeholders and untranslated strings beLingoLint compares your locale files and finds missing keys, broken placeholders, mismatched HTML and untranslated strings. Every locale gets a health score, and the CLI fails your CI when it matters. Runs locally, no account, MIT licensed. fore they ship. - wpfsg/lingolint

Free

Launch tags:Open Source•Developer Tools•GitHub

Launch Team

Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free

Promoted

Maker

📌

Hi everyone, maker here. I built LingoLint after shipping one too many releases where a translation was missing a placeholder and nobody noticed until a user in Germany saw "Total: {amount}" on their invoice. It works like a linter: point it at your locale folder and it reports missing keys, broken placeholders, unclosed HTML tags, untranslated strings and more, with a 0 to 100 health score per language. Drop it into CI and it fails the build when something serious slips in. Everything runs locally. There's an optional AI review mode with your own API key for the things static rules can't catch, like wrong meaning or tone. Try it in the browser without installing anything, or run npx lingolint scan on your project. I'd love to hear what breaks for you.

Report

2mo ago

Reviews