kazuya kawaguchi
kazuya kawaguchi
related #19
Thanks! This issue was reproduced in my environment. I'll try to fix this issue!
As a result of investigation, it was caused by code due to dynamic importing of `import` of `src/main.js`. I have reported to Vue CLI issue it. https://github.com/vuejs/vue-cli/issues/3309 In generally, `src/main.(js|ts)`...
> * Started a repro here (https://codesandbox.io/s/nuxt3-i18n-repro-1451-xvc1k3?file=/package.json), however the `` `@change` handler doesn't work at all for some reason? If anyone could help me debug, this codesandbox has everything else...
current v8 alpha version, differentDomains has not been implemented yet. We will implement it after v8 alpha.1 is released. Thanks!
@rchl Thank you for your mention! Great works! but, sorry, I forgot to tell you 🙇 I previously released `vue-i18n-bridge` for vue 2. that is back-ported from vue-i18n-next composition API...
> So the question is, should this module create its own composition API like in this PR or maybe expose a wrapper for `vue-i18n` API that also adds extra properties....
current v8 alpha version, i18n custom block has not been implemented yet. We will implement it after v8 alpha.1 is released. Thanks!
In v8.0.0-beta.1 or later, this option is deprecated. Per component translations is enabled on default. Thanks! https://v8.i18n.nuxtjs.org/guide/migrating#deprecated-vuei18nloader-option