I Built a VS Code Extension to Detect Missing i18n Keys Before Production

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 c