fix(deps): update dependency vue-i18n to v9.2.0 #2210
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#2210
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/vue-i18n-9.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
9.2.0-beta.40
->9.2.0
Release Notes
intlify/vue-i18n-next
v9.2.0
Compare 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
messages
option ofcreateI18n
and 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-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 defaultFrom Vue I18n v9.2, the
globalInjection
option defaults totrue
. If you localize by global scope using$t
in your template, you no longer need to set this option.useI18n
in Legacy API modeWe 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 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
globalInjection
option default value (@kazupon)#940 feat: Support
useI18n
for 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)
useI18n
on Legacy API mode (@kazupon)🐛 Bug Fixes (36)
d.ts
breaking (@kazupon)📝 Documentation (37)
Stdio
forStudio
(@FMGordillo)defaultSFCLang
andglobalSFCScope
to sfc (@userquin)Contributers: 35
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 Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://2210-renovate-vue-i18n-9-x--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
CI failure seems unrelated.