vue-i18n
vue-i18n copied to clipboard
Vue I18n for Vue 3
### Clear and concise description of the problem Adding keys manually is annoying and extracting them with [Spittal/vue-i18n-extract](https://github.com/Spittal/vue-i18n-extract) is not always possible. ### Suggested solution i18next has a solution where...
### Reporting a bug? ``` import { ref } from 'vue'; import { useI18n } from 'vue-i18n'; const { t } = useI18n(); const columns = ref([ { name: 'code',...
removed .global method as it does not exist
### Clear and concise description of the problem `Intl.NumberFormat` supports `Number`, `BigInt`, and `String` as a number parameter. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/format > A Number, BigInt, or string, to format. Strings are parsed...
### Reporting a bug? The `v-t` only works with local defined messages if `useI18n` is called in the `setup` of the component. This does not work: ```vue { "en": {...
### Reporting a bug? Given that vuei18n runs in legacy mode and composition is also enabled during ssr the translations are always empty when useI18n is being invoked inside component...
### Reporting a bug? We have been utilizing multiple Vue root instances created with `new Vue({})` on the same page successfully. However, when upgrading to Vue 2.7 and implementing the...
### Reporting a bug? Adding yaml load support for Vite breaks `vue-i18n` and `@nuxtjs/i18n`. # Steps to reproduce 1. `git clone https://github.com/mzenz/nuxt-i18n-ssg-bug.git` 2. `git switch dev` 3. `yarn install` 4....
### Clear and concise description of the problem In version 8 I was able to format numbers with `` component to any locale I specify in `locale` property. All I...
### Reporting a bug? Placeholder for testing environment, is not replaced, development environment is replaced normally ### Expected behavior Placeholder for testing environment is replaced, ### Reproduction None ### System...