You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated to the v3, which now uses Nuxt I18n for its own component translations. Since this update, my existing i18n configuration no longer works as expected. It seems the framework’s new i18n setup conflicts with or overrides my own translations, and I’m unable to figure out how to properly extend its default localization to include my own.
Could you please provide guidance on how to configure or extend the new i18n setup so that my existing translations remain functional?
The text was updated successfully, but these errors were encountered:
Why do you want to extend a language? This i18n system is only there to translate the internals of the Nuxt UI components. If you want to translate your app, you can use Nuxt i18n and define your own locales.
Description
I recently updated to the v3, which now uses Nuxt I18n for its own component translations. Since this update, my existing i18n configuration no longer works as expected. It seems the framework’s new i18n setup conflicts with or overrides my own translations, and I’m unable to figure out how to properly extend its default localization to include my own.
Could you please provide guidance on how to configure or extend the new i18n setup so that my existing translations remain functional?
The text was updated successfully, but these errors were encountered: