Localization bugs usually do not look like bugs at first.

They sit inside JSON, YAML, CSV, or resource files as ordinary strings. A missing key, a renamed placeholder, a translation file that slowly falls out of sync with the source language. Nothing dramatic. Nothing that immediately looks like a broken build.

Then one day the UI ships in another language, and the problem becomes visible.

That is why I started building LocaLint , a small open-source tool for checking localization files before these issues reach users.

The idea is simple: translation files should be treated less like passive text and more like part of the codebase.

We already lint code, format files, check configs, and run tests before shipping.…