Replies: 5 comments 4 replies
-
I also try this, but still get error import VueI18nPlugin from '@intlify/unplugin-vue-i18n';
export default defineNuxtConfig({
vite: {
resolve: {
alias: {
'vue-i18n': 'vue-i18n/dist/vue-i18n.esm-bundler.js',
},
},
},
}) |
Beta Was this translation helpful? Give feedback.
-
Would you be able to share more context about your i18n usage (or better, if you can provide a repoduction) please? |
Beta Was this translation helpful? Give feedback.
-
Hi @larsalbrecht, We have similar situation, I need dynamic fetch translations, finally I use patch-package to patch I replace
Maybe it's not a good solution, but it can work, you can try it. |
Beta Was this translation helpful? Give feedback.
-
In production, it's recommended that all resources be precompiled if possible. The CLI to precompile resouces can be found here: And here is an example using dynamic loading in conjunction with back-end These may be helpful for you |
Beta Was this translation helpful? Give feedback.
-
Hello, About this topic, is there any doc about the pre compilation purpose and configuration (except https://v8.i18n.nuxtjs.org/options/misc/#precompile) ? I'm asking because I'm trying to migrate from nuxt2 to nuxt3, I'm using @nuxtjs/i18n@edge, and I'm a little bit surprise that a precompile call is done to the server. So is it possible to disable it ? And what is the potential lost ? Regards |
Beta Was this translation helpful? Give feedback.
-
When production, I got error
The message format compilation is not supported in this build. Because message compiler isn't included. You need to pre-compilation all message format.
,but I don't know how to disabled pre-compilation,
Seems this option can not work.
Beta Was this translation helpful? Give feedback.
All reactions