LocatorJS for translation keys—useful niche, but i18n tooling isn't a pain point at scale.
Frontend developers working with i18next internationalization in large projects.
LocatorJS · react-localize-redux · i18next DevTools
In larger projects, I often found myself searching through multiple JSON files to figure out which key was rendering a specific piece of text. Global search works, but it’s slow and sometimes noisy, especially when keys are reused or structured deeply.
The idea was inspired by LocatorJS, which lets you click a component in the browser and jump to its source file. I liked that workflow and wanted something similar, but focused specifically on translation keys.
LocaterJs Link https://www.locatorjs.com/ in case u did not know it
Select text, hit ⌘⇧T and the translated text is auto-pasted where you're typing — brutally simple and exactly the UX fix this tiny pain point needs. The BYO OpenAI/Claude key and local handling is the smartest privacy move here, but this is still an incremental utility rather than a new category; per-app presets, offline options, or smarter context handling would make it stand out.
One-click ROM translation with smart font patching when manual hex editing dominated before.
It hooks into your build process, finds t(...) calls, and only generates missing translations via an LLM while preserving hand-edited entries — useful ergonomics many i18n tools skip. Comes with Vite/Webpack plugins, watch/batching modes and unused-key cleanup; the hard parts left to you are translation quality, API cost, and secrets management.
Hotkey-first proofreading/translation, but Grammarly and DeepL hotkeys already do this.
Audio translation tool, but Whisper + translation APIs already commoditized this.
Clever three-key sequence detection makes Copilot key useful again for devs.
