kazuya kawaguchi

`@vue/composition-api` is optionaled in vue-i18n-bridge from v9.2.0-beta.39 https://github.com/intlify/vue-i18n-next/blame/master/packages/vue-i18n-bridge/package.json#L79-L83 if you need vue-i18n-bridge in Vue 2.7, it doesn't need the installation.

Thank you for your reporting! Unfortunately, We could not reproduce this issue. 😞 We need minimum reproduction codes to resolve this issue. Could you give it to us, please? 🙏

I’m forcusing on nuxt/i18n. And currently, I’m developing core library for nuxt/i18n and it will be able to use as vue plugin library.

Thank you for your reporting! I could reproduce this issue. I'll try to fix. :)

Hmm... In minimum webpack 5 env, I could not reproduce. https://github.com/intlify/vue-next-webpack-preview/tree/wp5 It's strange... 🤔 BTW, We don't need to install `json5` module, because JSON5 parser is included in `@intlify/vue-i18n-loader`.

Thank you for your reporting! This issue is weird ... 🤔 I need to understand about sourcemap of unocss.

Yeah, you're right. The structure of docs in vue-i18n v9 is intentional. First of all, the docs are also written on a legacy basis to make it easier to migrate...

@matthew-white Thank you for your comments! ❤️ > Let me know if I can help with any of this! For example, I could help contribute documentation: we are very happy...

Thank you for your reporting! I seem that the i18n instance is created with `createI18n` with `legacy: true` option. The `global` property can refer to Composer or VueI18n, as described...

sorry, I'm focusing on nuxtjs/i18n for v8 alpha release. please Type definitions in vue-i18n are really complex. I’m not a full-time OSS yet, so it may take some time until...