Building Internal Tooling for Localization
Why we wrote our own i18n parity checker instead of using a service.
Most localization platforms expect you to use their format, their workflow, their billing tier. We wanted JSON files in git and a checker that fails CI when a key is missing.
Forty lines of TypeScript later, we have exactly that. It flattens every locale file into dot-notation, compares against the source-of-truth English, and prints what's missing or extra.
It's not impressive. It's small. That's the whole point.