Changes for `i18next-vue` v3 about i18next-vue HOT 1 CLOSED

I talked to some colleagues. They use i18nOptions a lot and almost exclusively to set the keyPrefix for the component.
They agree with the general direction of using useTranslation() exclusively for this, but would like a smoother transition, which does not require converting all existing components at once to switch to i18next-vue version 3.

We now have the idea to drop support for i18nOptions messages, but keep supporting the other options under a legacy flag for this plugin. i18nOptions will continue to influence $t for the current component in v3.
i18nOptions would no longer influence useTranslation(), which would now use the i18next defaults set in i18next.init() - and of course explicit values (namespace, ...) passed to it.

For the next major version v4 we would then completely drop i18nOptions support. So v3 is a version supporting both, allowing converting components incrementally over to useTranslation().

from i18next-vue.