Why is the options API deprecated?

[telion2]

I just noticed this alert in my browser:
[intlify] Legacy API mode has been deprecated in v11. Use Composition API mode instead.
About how to use the Composition API mode, see https://vue-i18n.intlify.dev/guide/advanced/composition.html

Not sure what you exactly mean with Legacy API, but if you mean that the Options API of Vue is deprecated, then I do not see a trace of that in the docs:
https://vuejs.org/guide/introduction.html#api-styles

=> Do you really mean that the options API is deprecated in i18n?
==> if that is the case: Why? I like using the option API and don't like to use the composition API.
I like using i18n in the options API version for 2 reasons:

• I am used to it and I know what I am doing
• Switching to composition API forces me and my team to partly relearn Vue and development is slowed down
• The Composition Variant is a lot more verbose than the options API. (I just use [this.]$t("...") and it works)

[Safirion]

Same here... Option API is a more structured and clearer than the composition API.

I don't understand the decision that led to the drop of support...

[M1CK431]

I totally share this frustration. The Vue team has been very clear that the Options API is not deprecated and remains a fully supported, first-class API style. Yet, switching vue-i18n to composition mode (to silence the v11 warning) silently breaks component-scoped translations — <i18n> blocks and the i18n component option simply stop working when using the Options API. This forces developers to either live with the warning, or painfully refactor every single component to use useI18n() and replace $t() calls accordingly.

To address exactly this situation, I created vite-plugin-vue-i18n-sfc-auto-import.

The plugin transparently injects the necessary useI18n() setup at Vite's build/transform step, so that component-scoped translations keep working seamlessly with the Options API, even with vue-i18n composition mode enabled — no console warnings, no breaking changes, no codebase refactoring. You just configure it once in your vite.config.js and continue writing your SFCs exactly as you always have, using $t("...") as usual.

If you're stuck in this situation, feel free to give it a try!