chore(deps): update dependency vue-i18n to v11 #1197
Merged
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:
^10.0.5
->^11.0.1
Release Notes
intlify/vue-i18n (vue-i18n)
v11.0.1
Compare Source
This changelog is generated by GitHub Releases
What's Changed
⚡ Improvement Features
Full Changelog: intlify/vue-i18n@v11.0.0...v11.0.1
v11.0.0
Compare Source
This changelog is generated by GitHub Releases
What's Changed
Deprecate Legacy API mode
The Legacy API mode was the API mode compatible with v8 for Vue 2. When v9 was released, the Legacy API was provided to smooth the migration from v8 to v9.
Legacy API mode will be deprecated in v11, as previous vue-i18n releases have already provided the following to support migration to Composition API mode
For compatibility, Legacy API mode still works in v11, but will be removed entirely in v12, so Legacy API mode will not work after that version.
Deprecate Custom Directive
v-t
The advantage of
v-t
was that it could optimize performance using the vue compiler transform and the pre-translation ofvue-i18n-extension
.This feature was supported from Vue 2.
About details see the blog article
In Vue 3, due to the Composition API, the pre-translation of
vue-i18n-extension
is now limited only for global scope.In addition, Vue 3 Virtual DOM optimization has been introduced, and the optimization provided by
vue-i18n-extension
is no longer very effective. We need to require settings for SSR, the benefits of usingv-t
have disappeared. And DX of templates usingv-t
is not good. Custom directives do not work with key completion in editors (e.g. vscode).For compatibility,
v-t
mode still works in v11, but will be removed entirely in v12, sov-t
will not work after that version.Drop
tc
and$tc
for Legacy API modeThese APIs had already deprecated in warning about being dropped in v11. docs says
Vue I18n maintenance Status
Vue I18n v8 is no longer supported after 2025. Vue I18n v9 and Vue I18n v10 is in maintenance mode after 2025 July.
With the release of Vue I18n v11, that version will become mainstream.
The maintenance detail status of Vue I18n v9 and Vue I18n v10 is as follows:
You can check the maintenance status on the docs
❗ Braeking Changes
$tc
andtc
by @kazupon in https://github.com/intlify/vue-i18n/pull/2017v-t
custom directive by @kazupon in https://github.com/intlify/vue-i18n/pull/2045⚡ Improvement Features
tm
function should acceptDefineLocaleMessage
key type by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/2014🔒 Security Fixes
📝️ Documentations
👋 New Contributors
Full Changelog: intlify/vue-i18n@v10.0.4...v11.0.0
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.