t('common:user.profile.title')… and now you just hope that key actually exists.
On any serious i18next project, you end up typing keys blind. Does the key exist? In which namespace? What's its value? Is it translated in every language, or just English? To find out, you open en/common.json, hit Ctrl+F, scroll, come back. Multiply by 200 keys and 5 locales and it's a daily tax on your focus.
The real problem isn't i18next. It's that your keys and your translations live in files your editor treats as dead text. A string in the code, a JSON next door, and zero link between the two.
I've been maintaining and heavily extending a JetBrains plugin (I18n Support Plus) to restore that link. The idea fits in one sentence: your i18n keys become first-class references in the IDE, exactly like code symbols. Here's concretely what that changes.
1. See a key's status without opening a single file
