f you’ve ever shipped a UI bug where users see something like this:
settings.labels.confirm_action_final_v2_FIXED
…then you already know how painful localization bugs can be.
Missing i18n keys are one of those problems that seem small until they hit production. They slip through code review, hide inside large translation files, and usually appear when it’s too late.
After dealing with this frustration too many times, I decided to build a better solution.
The Problem
In multilingual apps, it’s easy to:
Reference translation keys that don’t exist
Leave hardcoded untranslated strings in components
Break localization during refactoring without noticing
Most teams catch these issues manually, which is slow, error-prone, and honestly exhausting.
The Solution: Localization Scanner for VS Code
I created a VS Code extension that scans your project and detects:
- Missing translation keys
- Broken localization references
- Hardcoded untranslated UI strings
Instead of manually searching JSON files and comparing keys, the extension flags issues directly inside VS Code while you work.
Why I Built It
I wanted something that would:
Save debugging time
Prevent embarrassing production bugs
Help teams catch localization issues earlier in development
Localization should be automatic and reliable not a guessing game.
Who It’s For
This tool is useful if you build apps with:
React
Vue
Next.js
Any frontend app using i18n translation files
What’s Next
I’m actively improving the extension and would love feedback from developers working on multilingual apps.
What’s the most frustrating localization bug you’ve dealt with?
Read more and try it here: https://dev.to/dev_harry/how-to-find-missing-i18n-keys-without-losing-your-mind-or-your-job-1jff
or download it here
https://marketplace.visualstudio.com/items?itemName=devharry.localizations-scanner
Top comments (0)