This repository was archived by the owner on Mar 7, 2023. It is now read-only.
fix(deps): update dependency vue-i18n to v9.2.2#9
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
renovate
bot
force-pushed
the
renovate/vue-i18n-9.x
branch
from
84eb8e1 to
7a80c26
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/vue-i18n-9.x
branch
from
7a80c26 to
51334e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.1.9->9.2.2Release Notes
intlify/vue-i18n-next
v9.2.2Compare Source
🐛 Bug Fixes
vue-i18n-coreCommitters: 1
v9.2.1Compare Source
🐛 Bug Fixes
vue-i18n-core📝 Documentation
petite-vue-i18nCommitters: 6
v9.2.0Compare Source
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
messagesoption ofcreateI18nand complementing with APIs such ast.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-bridgeto support Vue 2 applications with Vue I18n v8.x migrate to Vue 3.vue-i18n-bridgeis 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
globalInjectionoption As defaultFrom Vue I18n v9.2, the
globalInjectionoption defaults totrue. If you localize by global scope using$tin your template, you no longer need to set this option.useI18nin Legacy API modeWe have supported for
useI18nin 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-bridgemodule 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-tWe have supported SSR for
v-t. If your Vue application usesv-t, you can support SSR without having to be aware in your Vue application.⭐ Features (15)
#1087 feat: support SSR for v-t (@kazupon)
#1062 feat: support Vue 2.7 for vue-i18n-bridge (@kazupon)
#974 feat: change
globalInjectionoption default value (@kazupon)#940 feat: Support
useI18nfor Legacy API mode (@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)
#733 support node native es modules (@kazupon)
#676 feat: bridge for vue-i18n@v8.26.1 or later (@kazupon)
#673 feat: export types (@kazupon)
#641 feat: support web components (@kazupon)
#623 feat: support Vue 3.2 (@kazupon)
#588 feat: petite-vue-i18n (@kazupon)
#508 feat: type-safe with global type definition (@kazupon)
#478 improvement: target component highlighting on i18n resources inspector (@kazupon)
#477 feat: custom message resolver (@kazupon)
💥 Breaking Change (3)
⚡ Improvement Features (30)
useI18non Legacy API mode (@kazupon)🐛 Bug Fixes (36)
d.tsbreaking (@kazupon)📝 Documentation (37)
StdioforStudio(@FMGordillo)defaultSFCLangandglobalSFCScopeto sfc (@userquin)Contributers: 35
v9.1.10Compare Source
v9.1.10 (2022-05-01)
⚡ Improvement Features
size-check-vue-i18n,vue-i18nCommitters: 1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.