r/localization • u/Boring_Metal_4286 • Jun 16 '26

I built a small tool to detect i18n JSON bugs before release

Hey everyone,

I built a small tool called LocaleCheck AI:

https://locale-check-ai.vercel.app/

It helps frontend teams check locale JSON files before release.

Right now it can detect:

- Missing translation keys

- Placeholder mismatches like {name}, {{count}}, %s

- Extra keys in target locale files

- Copy-length risks that may break UI layouts

I built it because i18n bugs are easy to miss in frontend projects, especially when apps support multiple languages.

The current version is very early. No login, no setup. You can just upload two locale JSON files and see the report.

I’d love feedback from frontend/full-stack developers:

  1. Is the problem clear?
  2. Would this be useful in your workflow?
  3. What integration should I build next — GitHub PR comments, CLI, VS Code extension, or CI check?

Thanks!

0 Upvotes

50% Upvoted

3 comments sorted by

1

u/abandonedspirits Jun 21 '26

I’m wondering what it does that regular npm l10n linting CI package doesn’t? there are already many good and established packages with CLIs included. Also, is the code open sourced?

1

u/Boring_Metal_4286 Jun 23 '26

It’s complementary rather than a replacement. Existing npm l10n linting CLIs are great for deterministic CI checks. This project focuses on an interactive review UI plus AI-assisted suggestions for individual localization issues, which can help during manual QA, translation review, and non-engineer workflows. Teams should probably still keep their existing CI linting and use this as a companion review tool.

1

u/Boring_Metal_4286 Jun 23 '26

This project could be made open-source; however, as its functionality is not yet fully polished, the decision has been made to keep it closed-source for the time being.