Releases: intlify/vue-i18n
v9.3.0-beta.6
v9.3.0-beta.5
v9.3.0-beta.4
v9.3.0-beta.4 (2022-09-28)
🐛 Bug Fixes
vue-i18n-core- #1177 fix:using the better Fragment detection(#1122) (@littleboarx)
⚡ Improvement Features
Committers: 2
- @littleboarx
- kazuya kawaguchi (@kazupon)
v9.3.0-beta.3
v9.3.0-beta.2
v9.3.0-beta.2 (2022-08-31)
⭐ Features
core-base,core,devtools-if,message-compiler,petite-vue-i18n,shared,vue-devtools,vue-i18n-bridge,vue-i18n-core,vue-i18n
⚡ Improvement Features
Committers: 1
- kazuya kawaguchi (@kazupon)
v9.3.0-beta.1
v9.3.0-beta.1 (2022-08-28)
⭐ Features
core-base,core,devtools-if,message-compiler,petite-vue-i18n,shared,size-check-core,size-check-petite-vue-i18n,size-check-vue-i18n,vue-devtools,vue-i18n-bridge,vue-i18n-core,vue-i18n
Committers: 1
- kazuya kawaguchi (@kazupon)
v9.3.0-beta.0
v9.3.0-beta.0 (2022-08-28)
This release is for native ESM support preparation.
📝 Documentation
- #1129 Add information about the pluralization option for the Composition API (@domoratskii)
Committers: 1
- Roman Domoratskii (@domoratskii)
v9.2.2
v9.2.1
v9.2.1 (2022-08-05)
🐛 Bug Fixes
📝 Documentation
- Other
- #1106 fix(typo): update IE note on date formatting section (@jcfauchet)
- #1105 i18n.global.locale is a ref (@Cygnut)
- #1099 Editorial fixes (@xfq)
- #1098 Editorial fix (@xfq)
- #1097 Fix(docs): Fixing Typo in optimization.md (@JULO01)
- #1094 Fix documentation typography (@sey)
- #1041 replace docs site with vitepress v1 (@kazupon)
petite-vue-i18n
Committers: 6
v9.2.0
v9.2.0 (2022-08-01)
We are excited to announce the release of Vue I18n v9.2 !! This release includes many new features, bug fixes, improvements, and document fixes.
We had commited with 35 contributors. Thanks for your contributing ❤️
In the following, we introduce some of the new features:
More TypeScript supporting
From Vue I18n v9.2, we have improved TypeScript support. This allows type checking of resources specified in the messages option of createI18n and complementing with APIs such as t.
The following images is the resoureces type-checked:
The following gif image is the API completion working:
For more information on how to setup the system, please read the docs
Web Components
WebComponents has been supported since Vue 3.2. You can support your Vue Component with Vue I18n as well.
About details, See more the docs
Small size subset of Vue I18n
We have released petite-vue-i18n, a small size subset version of Vue I18n, as an experimental feature.
Only minimal functionality is provided in this module. you can reduce your Vue application bundle size with using this module. If you do not need to use all the features of Vue I18n, this module would be a good option.
About details, See more README
Bridging to Vue 3
We have released a module called vue-i18n-bridge to support Vue 2 applications with Vue I18n v8.x migrate to Vue 3.
vue-i18n-bridge is a module that is mostly compatible with the Vue I18n v9 API. It's an add-on to existing Vue I18n v8.26.1 or later + Vue 2 applications to take advantage of the Composition API provided in Vue I18n v9. This module would be able to support the progressive migration to Vue 3.
About details, See more the docs
globalInjection option As default
From Vue I18n v9.2, the globalInjection option defaults to true. If you localize by global scope using $t in your template, you no longer need to set this option.
useI18n in Legacy API mode
We have supported for useI18n in Legacy API mode. This feature would be useful if you want to migrate from the options API style to the Composition API style in your Vue 3 application.
About details, See more the docs
Vue 2.7
vue-i18n-bridge module for migration to Vue 3 of course supports Vue 2.7.
Instead of going from Vue 2.6 to Vue 3 directly, you can migrate your Vue applications using Vue I18n with a strategy of Vue 2.6, Vue 2.7, and then Vue 3 progressively.
SSR for v-t
We have supported SSR for v-t. If your Vue application uses v-t, you can support SSR without having to be aware in your Vue application.
⭐ Features (15)
-
#974 feat: change
globalInjectionoption default value (@kazupon) -
#838 feat: composer type definition extending (experimental feature) (@kazupon)
-
#811 feat: backport build-in components to vue-i18n-bridge from vue-i18n-next (@kazupon)
-
#676 feat: bridge for [email protected] or later (@kazupon)
-
#588 feat: petite-vue-i18n (@kazupon)
-
#478 improvement: target component highlighting on i18n resources inspector (@kazupon)
💥 Breaking Change (3)
- #757 breaking: revert import.browser fileds (@kazupon)
- #560 breaking: drop node v10 (@kazupon)
- #514 Fix FEATURE_ESM_BUNDLER_WARN flag can not be configured (@PeterAlfredLee)
⚡ Improvement Features (30)
- #1064 fix: slot resolving in render function (@kazupon)
- #1043 fix typo and polish (@lazzzis)
- #1022 improvement: allow custom block
useI18non Legacy API mode (@kazupon) - #983 fix(legacy): allow multi legacy i18n instance for bridge (@kazupon)
- #977 feat: release global scope (@kazupon)
- #973 fix(bridge): improvement writable install function for vue-i18n-routing (@kazupon)
- #929 improvement: tweak vue-i18n for SSR (@kazupon)
- #929 improvement: tweak vue-i18n for SSR (@kazupon)
- #907 fix: avoid undefined read (@kazupon)
- #903 fix: revert type test case change in strictI18n (@littleboarx)
- #879 fix: null element access (@kazupon)
- #876 fix: null access on mount hook (@kazupon)
- #861 improvement: export castToVueI18n for @intlity/vue-i18n-bridge (@kazupon)
- #780 improvement: vue-i18n-bridge installation at nuxt-bridge (@kazupon)
- #764 improvement: global injection for vue-i18n-bridge (@kazupon)
- #761 improvement: avoid vite ssrTransform bug (@kazupon)
- #742 fix: node esm for nuxt3 (@kazupon)
- #731 move to pnpm from yarn v1 (@kazupon)
- #709 improvement: support vue-i18n-loader bridge mode (@kazupon)
- #705 improvement: flag for vue-i18n-bridge (@kazupon)
- #700 improvement: expose type casting API for Legacy mode (@kazupon)
- #619 improvement: bundle source map at message-compiler (@kazupon)
- #584 improvement: reduce size (@kazupon)
- #583 improvement: deprecated VUE_I18N_PROD_DEVTOOLS feature flag (@kazupon)
- #578 support for Vue 3.1 (@kazupon)
- #545 Allow number and boolean in args of number formatting (@yannbriancon)
- #541 Add number formatting missing type definition (@yannbriancon)
- #489 Type safe improvements (@kazupon)
- [#593]...