Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

I built a CLI to catch i18n bugs. It found 74 issues in my own app before they shipped

DEV Community·Francis Okocha-Ojeah·23 days ago
#J1W3Vg0O
#reactnative#i18n#cli#opensource#locale#react
Reading 0:00
15s threshold

We ship a React Native app in English and Portuguese. Every other release, someone would find a hardcoded English string or a missing translation key. Manual audits were slow, inconsistent, and honestly, error-prone. I was tired of it. So I built locale-lint . A zero‑config CLI that scans your entire codebase and catches the stuff we usually miss. I ran it on our production app. In less than half a second, it found 74 issues that I had completely overlooked. Keys that existed in English but not Portuguese. Labels that were still raw English. Stuff that would have shipped in the next release. Here’s exactly what it flagged in our app: What it detects Missing keys — e.g. English key missing from Portuguese Unused keys — can be safely cleaned up Undefined keys — called in code but missing from all locale files Hardcoded text — raw strings in JSX like <Text>Welcome</Text> Interpolation mismatches — e.g.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More