kazuya kawaguchi comments

Results 399 comments of


                                            kazuya kawaguchi

switchLocalePath

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.

[Feature Request] Namespaced translations

I think that this issue should be solved together with lazy loading. I’m working on nuxtjs/i18n for nuxt3. This has also given me a better understanding of the i18n routing....

`const { t } = useI18n()` does not work

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

<i18n-t> message scope resolution should start at current component

Thank you for your reporting! we need to revise the internal structure of vue-i18n a bit, so to solve this issue. And we need to investigate if Vue provides a...

`version.split is not a function` on vite build

@Vestibule Thank you for your reporting! I've tried to reproduce your reporting! Unfortunately, I could not that issue... 😞 I've put the repro repo https://github.com/kazupon/vue-i18n-next-repro-719 Could you modify some reproduction...

`version.split is not a function` on vite build

>npmPackages: vue: ^3.1.4 => 3.2.9 vue-i18n: ^9.0.0 => 9.1.7 I noticed vue-i18n v9.0.x is used in your package.json Could you try to use the vue-i18n **v9.1.x** (latest v9.1.8) please?

`version.split is not a function` on vite build

Hmm... Could you try to build with minify off (`vite build --minify false`), please?

`version.split is not a function` on vite build

We can get the details of stacktrace.

`version.split is not a function` on vite build

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more information. Thanks!

VueI18N is not installed on production server

Could you give us your minimum reproduction repo, please?