Skip to content

fix(deps): update dependency vue-i18n to v9

sousuke0422 requested to merge renovate/vue-i18n-9.x into develop

This MR contains the following updates:

Package Change Age Adoption Passing Confidence
vue-i18n (source) 8.28.2 -> 9.2.2 age adoption passing confidence

Release Notes

intlify/vue-i18n-next

v9.2.2

Compare Source

🐛 Bug Fixes
  • vue-i18n-core
Committers: 1

v9.2.1

Compare Source

🐛 Bug Fixes
📝 Documentation
Committers: 6

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 of createI18n and complementing with APIs such as t.

The following images is the resoureces type-checked:

type check1 type check2

The following gif image is the API completion working:

completion

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)
💥 Breaking Change (3)
Improvement Features (30)
🐛 Bug Fixes (36)
📝 Documentation (37)
Contributers: 35

v9.1.10

Compare Source

v9.1.10 (2022-05-01)

Improvement Features
Committers: 1

v9.1.9

Compare Source

v9.1.9 (2021-10-06)

🐛 Bug Fixes
Committers: 1

v9.1.8

Compare Source

v9.1.8 (2021-10-04)

🐛 Bug Fixes
  • message-compiler, vue-i18n
Committers: 1

v9.1.7

Compare Source

🐛 Bug Fixes
Committers: 1

v9.1.6

Compare Source

🐛 Bug Fixes
Committers: 1

v9.1.5

Compare Source

Improvement Features
Committers: 2

v9.1.4

Compare Source

Improvement Features
📝 Documentation
Committers: 2

v9.1.3

Compare Source

Improvement Features
  • core-base, vue-i18n
Committers: 1

v9.1.2

Compare Source

🐛 Bug Fixes
Committers: 1

v9.1.1

Compare Source

🐛 Bug Fixes
Committers: 1

v9.1.0

Compare Source

Features
🐛 Bug Fixes
Improvement Features
💥 Breaking Change
  • core-base, size-check-vue-i18n, vue-i18n

To provide experimental features for @intlify/devtools, feature flags have been separated as follows.

  • __VUE_I18N_MROD_DEVTOOLS__: enable/disable vue-devtools support in production, default: false
  • __INTLIFY_MROD_DEVTOOLS__: enable/disable @intlify/devtools support in production, default: false

Previously, __INTLIFY_MROD_DEVTOOLS__ setting flagged the use of both vue-devtools and @intlify/devtools in production.

In later v9.1, The feature flags for vue-devtools are now enabled/disabled by setting __VUE_I18N_MROD_DEVTOOLS__.

📝 Documentation
Committers: 6

v9.0.0

Compare Source

See the below link: https://blog.intlify.dev/posts/vue-i18n-9.html


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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Merge request reports

Loading