chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

renovate · 2024-12-02T19:53:25Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vue-i18n-legacy (source)	`8` -> `11`

GitHub Vulnerability Alerts

CVE-2024-52809

Vulnerability type

XSS

Description

vue-i18n can be passed locale messages to createI18n or useI18n.
we can then translate them using t and $t.
vue-i18n has its own syntax for local messages, and uses a message compiler to generate AST.
In order to maximize the performance of the translation function, vue-i18n uses bundler plugins such as @intlify/unplugin-vue-i18n and bulder to convert the AST in advance when building the application.
By using that AST as the locale message, it is no longer necessary to compile, and it is possible to translate using the AST.

The AST generated by the message compiler has special properties for each node in the AST tree to maximize performance. In the PoC example below, it is a static property, but that is just one of the optimizations.
About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts

In general, the locale messages of vue-i18n are optimized during production builds using @intlify/unplugin-vue-i18n,
so there is always a property that is attached during optimization like this time.
But if you are using a locale message AST in development mode or your own, there is a possibility of XSS if a third party injects.

Reproduce (PoC)

<!doctype html>
<html>
  <head>
    <meta charset="utf-8" />
    <title>vue-i18n XSS</title>
    <script src="https://unpkg.com/vue@3"></script>
    <script src="https://unpkg.com/vue-i18n@10"></script>
    <!-- Scripts that perform prototype contamination, such as being distributed from malicious hosting sites or injected through supply chain attacks, etc. -->
    <script>
      /**
       * Prototype pollution vulnerability with `Object.prototype`.
       * The 'static' property is part of the optimized AST generated by the vue-i18n message compiler.
       * About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts
       *
       * In general, the locale messages of vue-i18n are optimized during production builds using `@intlify/unplugin-vue-i18n`,
       * so there is always a property that is attached during optimization like this time.
       * But if you are using a locale message AST in development or your own, there is a possibility of XSS if a third party injects prototype pollution code.
       */
      Object.defineProperty(Object.prototype, 'static', {
        configurable: true,
        get() {
          alert('prototype polluted!')
          return 'prototype pollution'
        }
      })
    </script> 
 </head>
  <body>
    <div id="app">
      <p>{{ t('hello') }}</p>
    </div>
    <script>
      const { createApp } = Vue
      const { createI18n, useI18n } = VueI18n

      // AST style locale message, which build by `@intlify/unplugin-vue-i18n`
      const en = {
        hello: {
          type: 0,
          body: {
            items: [
              {
                type: 3,
                value: 'hello world!'
              }
            ]
          }
        }
      }

      const i18n = createI18n({
        legacy: false,
        locale: 'en',
        messages: {
          en
        }
      })

      const app = createApp({
        setup() {
          const { t } = useI18n()
          return { t }
        }
      })
      app.use(i18n)
      app.mount('#app')
    </script>
  </body>
</html>

Workarounds

Before v10.0.0, we can work around this vulnerability by using the regular compilation (jit: false of @intlify/unplugin-vue-i18n plugin configuration) way instead of jit compilation.

jit compilation: https://vue-i18n.intlify.dev/guide/advanced/optimization.html#jit-compilation
bundler plugin option: https://github.com/intlify/bundle-tools/tree/main/packages/unplugin-vue-i18n#jitcompilation

References

Simillar case: Vue 2 XSS vulnerability with prototype pollution

CVE-2025-27597

Vulnerability type:
Prototype Pollution

Vulnerability Location(s):

# v9.1
node_modules/@&#8203;intlify/message-resolver/index.js

# v9.2 or later
node_modules/@&#8203;intlify/vue-i18n-core/index.js

Description:

The latest version of @intlify/message-resolver (9.1) and @intlify/vue-i18n-core (9.2 or later), (previous versions might also affected), is vulnerable to Prototype Pollution through the entry function(s) handleFlatJson. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence.

Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.

PoC:

// install the package with the latest version
~$ npm install @&#8203;intlify/[email protected]
// run the script mentioned below 
~$ node poc.js
//The expected output (if the code still vulnerable) is below. 
// Note that the output may slightly differs from function to another.
Before Attack:  {}
After Attack:  {"pollutedKey":123}

// poc.js
(async () => {
    const lib = await import('@&#8203;intlify/message-resolver');
    var someObj = {}
    console.log("Before Attack: ", JSON.stringify({}.__proto__));
    try {
        // for multiple functions, uncomment only one for each execution.
        lib.handleFlatJson ({ "__proto__.pollutedKey": "pollutedValue" })
    } catch (e) { }
    console.log("After Attack: ", JSON.stringify({}.__proto__));
    delete Object.prototype.pollutedKey;
})();

Release Notes

intlify/vue-i18n (vue-i18n-legacy)

`v11.1.3`

Compare Source

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v11 by @kazupon in https://github.com/intlify/vue-i18n/pull/2159

⚡ Improvement Features

fix: duplicate generated type config naming by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/2158

Full Changelog: intlify/vue-i18n@v11.1.2...v11.1.3

`v11.1.2`

Compare Source

What's Changed

🔒 Security Fixes

fix: prototype pollution in handleFlatJson, about details see GHSA-p2ph-7g93-hw3m

Full Changelog: intlify/vue-i18n@v11.1.1...v11.1.2

`v11.1.1`

Compare Source

Full Changelog: intlify/vue-i18n@v11.1.0...v11.1.1

`v11.1.0`

Compare Source

What's Changed

🌟 Features

feat: configurable ComponentCustomProperties['$i18n'] type by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/2094

📝️ Documentations

fix: vue-i18n v8 EOL by @kazupon in https://github.com/intlify/vue-i18n/pull/2060

Full Changelog: intlify/vue-i18n@v11.0.1...v11.1.0

`v11.0.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: v-t custom directive warning when it will run by @kazupon in https://github.com/intlify/vue-i18n/pull/2057

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

Migration from Legacy API mode to Composition API mode, see the docs
Composition API usage, see the docs

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 of vue-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 using v-t have disappeared. And DX of templates using v-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, so v-t will not work after that version.

Drop `tc` and `$tc` for Legacy API mode

These 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

❗ Breaking Changes

feat!: deprecate Legacy API mode by @kazupon in https://github.com/intlify/vue-i18n/pull/2016
breaking: drop $tc and tc by @kazupon in https://github.com/intlify/vue-i18n/pull/2017
feat!: deprecate v-t custom directive by @kazupon in https://github.com/intlify/vue-i18n/pull/2045

⚡ Improvement Features

fix: tm function should accept DefineLocaleMessage key type by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/2014

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v10 by @kazupon in https://github.com/intlify/vue-i18n/pull/2160

Full Changelog: intlify/vue-i18n@v10.0.6...v10.0.7

`v10.0.6`

Compare Source

What's Changed

🔒 Security Fixes

fix: prototype pollution in handleFlatJson, about details see GHSA-p2ph-7g93-hw3m

Full Changelog: intlify/vue-i18n@v10.0.5...v10.0.6

`v10.0.5`

Compare Source

What's Changed

🔒 Security Fixes

fix: XSS vulnerability with prototype pollution on AST: GHSA-9r9m-ffp6-9x4v
fix: prototype pollusion on deepCopy: GHSA-hjwq-mjwj-4x6c

Full Changelog: intlify/vue-i18n@v10.0.4...v10.0.5

`v10.0.4`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: cannot resolve empty string on plural by @kazupon in https://github.com/intlify/vue-i18n/pull/1985

📝️ Documentations

Add petite-vue-i18n package to README by @vikingair in https://github.com/intlify/vue-i18n/pull/1971

New Contributors

@vikingair made their first contribution in https://github.com/intlify/vue-i18n/pull/1971

Full Changelog: intlify/vue-i18n@v10.0.3...v10.0.4

`v10.0.3`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix(petite-vue-i18n): cannot register correctly message resolver and locale fallbacker by @kazupon in https://github.com/intlify/vue-i18n/pull/1967

📝️ Documentations

docs: add unplugin-vue-i18n setting for petite-vue-i18n by @kazupon in https://github.com/intlify/vue-i18n/pull/1968

Full Changelog: intlify/vue-i18n@v10.0.2...v10.0.3

`v10.0.2`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: revert #1379 by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/1953
fix: messages deepCopy mutates src arguments by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/1947

📝️ Documentations

docs: add team members by @kazupon in https://github.com/intlify/vue-i18n/pull/1951
docs: add how to use shared locale messages on composition api by @kazupon in https://github.com/intlify/vue-i18n/pull/1964

Full Changelog: intlify/vue-i18n@v10.0.1...v10.0.2

`v10.0.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: petite-vue-i18n type errors by @TPORL in https://github.com/intlify/vue-i18n/pull/1945

New Contributors

@TPORL made their first contribution in https://github.com/intlify/vue-i18n/pull/1945

Full Changelog: intlify/vue-i18n@v10.0.0...v10.0.1

`v10.0.0`

Compare Source

fix: vue-i18n type definition for vue package by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/1919

Full Changelog: intlify/vue-i18n@v9.13.1...v9.14.0

`v9.13.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix(message-compiler): cannot resolve none-identifier characters at linked key by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1813

Full Changelog: intlify/vue-i18n@v9.13.0...v9.13.1

`v9.13.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚠️ Deprecated Features

fix: EOL announcement warning for vue-i18n-bridge by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1800

⚡ Improvement Features

fix: not throw warnings when using implicit fallback by @ShinnosukeKomiya in https://github.com/intlify/vue-i18n-next/pull/1798

📝️ Documentations

fix: spelling by @DamageESP in https://github.com/intlify/vue-i18n-next/pull/1802
docs: improve documentation by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1801
docs: fix dead link on menu by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1804

New Contributors

@ShinnosukeKomiya made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1798
@DamageESP made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1802

Full Changelog: intlify/vue-i18n@v9.12.1...v9.13.0

`v9.12.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: compile error for key with included hyphen in named interpolation by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1797

👕 Refactoring

refactor: tokenizer by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1799

Full Changelog: intlify/vue-i18n@v9.12.0...v9.12.1

`v9.12.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: deprecate named interpolation with modulo syntax by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1795

Full Changelog: intlify/vue-i18n@v9.11.1...v9.12.0

`v9.11.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: regression triple slash including in .d.ts by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1794

Full Changelog: intlify/vue-i18n@v9.11.0...v9.11.1

`v9.11.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: number and date format components not using scope prop by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1786

New Contributors

@xuanzhi33 made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1767
@YoshiYo made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1781

Full Changelog: intlify/vue-i18n@v9.10.2...v9.11.0

`v9.10.2`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: manually add triple slash directive to message-compiler by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1766

New Contributors

@shinGangan made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1763

Full Changelog: intlify/vue-i18n@v9.10.1...v9.10.2

`v9.10.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

chore(fix): #1630 make the install function synchronous to be aligned… by @k-paxian in https://github.com/intlify/vue-i18n-next/pull/1631

📝️ Documentations

docs: wrong te docs by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1753

New Contributors

@k-paxian made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1631

Full Changelog: intlify/vue-i18n@v9.10.0...v9.10.1

`v9.10.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: Support for te behavior compatibility before v9.6 by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1751

📝️ Documentations

docs: update description of Nuxt I18n and its status by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1739

New Contributors

@twolfvb made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1732
@ismailarilik made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1722

Full Changelog: intlify/vue-i18n@v9.9.1...v9.10.0

`v9.9.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: key-value style messages broken after merging (#1717) by @chojnicki in https://github.com/intlify/vue-i18n-next/pull/1718

📝️ Documentations

chore(typo): update injection.md by @quentinmcq in https://github.com/intlify/vue-i18n-next/pull/1716
Update syntax.md by @hinogi in https://github.com/intlify/vue-i18n-next/pull/1701

New Contributors

@chojnicki made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1718
@quentinmcq made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1716
@hinogi made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1701

Full Changelog: intlify/vue-i18n@v9.9.0...v9.9.1

`v9.9.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

Register vue jsx types in tsx test by @yyx990803 in https://github.com/intlify/vue-i18n-next/pull/1661
chore: improve Vue type definition appending by @NozomuIkuta in https://github.com/intlify/vue-i18n-next/pull/1671

📈 Performance Fixes

fix: lower memory usage by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1677

📝️ Documentations

Update installation.md by @KumJungMin in https://github.com/intlify/vue-i18n-next/pull/1676

New Contributors

@yyx990803 made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1661
@KumJungMin made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1676

Full Changelog: intlify/vue-i18n@v9.8.0...v9.9.0

`v9.8.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat: more strictly return type locale detector by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1640

Full Changelog: intlify/vue-i18n@v9.7.1...v9.8.0

`v9.7.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: tweak @intlify/core conditional exports by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1639

Full Changelog: intlify/vue-i18n@v9.7.0...v9.7.1

`v9.7.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat: export message merging utilities to shared module by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1635

Full Changelog: intlify/vue-i18n@v9.6.5...v9.7.0

`v9.6.5`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: Nuxt I18n type inference by @BobbieGoede in https://github.com/intlify/vue-i18n-next/pull/1628

New Contributors

@BobbieGoede made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1628

Full Changelog: intlify/vue-i18n@v9.6.4...v9.6.5

`v9.6.4`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: wrong source getting by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1624

Full Changelog: intlify/vue-i18n@v9.6.3...v9.6.4

`v9.6.3`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: adjust /* #__PURE__*/ comment timing by @newives in https://github.com/intlify/vue-i18n-next/pull/1623

New Contributors

@newives made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1623

Full Changelog: intlify/vue-i18n@v9.6.2...v9.6.3

`v9.6.2`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: return null for fucntion by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1617

Full Changelog: intlify/vue-i18n@v9.6.1...v9.6.2

`v9.6.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: more te logic strictly by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1612
fix: te fallback to root by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1613

Full Changelog: intlify/vue-i18n@v9.6.0...v9.6.1

`v9.6.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat!: support resource schema type definition for @intlfy/core-base (@intlify/core) by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1594

🐛 Bug Fixes

fix(examples): remove @vite-ignore magic comment by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1590
fix: cannot resolve flatjson messages when use setLocaleMessage by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1601
fix: strictly key exsisting with te by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1602

⚡ Improvement Features

fix: locale detector type definition by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1591

📝️ Documentations

docs: add example link by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1608

Full Changelog: intlify/vue-i18n@v9.5.0...v9.6.0

`v9.5.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat(core-base): support locale detector by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1566

🐛 Bug Fixes

Handle falsy values in i18n.te() by @BuuBux in https://github.com/intlify/vue-i18n-next/pull/1554
fix(core-base): wrong list index resolving on jit optimization by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1571
fix: support runtime module for node.js by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1573

📝️ Documentations

docs: fix typo in optimization.md by @Theiaz in https://github.com/intlify/vue-i18n-next/pull/1565
Fix typos in breaking.md doc by @piercemorris in https://github.com/intlify/vue-i18n-next/pull/1572

🍭 Examples

Update nuxt.config.ts in Nuxt 3 Minimal Starter Example by @ram-you in https://github.com/intlify/vue-i18n-next/pull/1553

New Contributors

@BuuBux made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1554
@Theiaz made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1565
@piercemorris made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1572

Full Changelog: intlify/vue-i18n@v9.4.1...v9.5.0

`v9.4.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: cannot resolve linked refer message by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1549
fix: cannot resolve linked refer message that has hypen by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1550
fix: type errors for core-base by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1551

📝️ Documentations

docs: add build.transpile option by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1548

Full Changelog: intlify/vue-i18n@v9.4.0...v9.4.1

`v9.4.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat(shared): support dist package for browser by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1527

🐛 Bug Fixes

fix(vue-i18n-bridge): peer dependency warning by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1536

⚡ Improvement Features

feat(core): optimize core package for node.js by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1530
fix: optimize tree-shaking for devtools packages by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1531
improvement: tweak compler registration and message condition on compile function by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1532

New Contributors

@ram-you made their first contribution in https://github.com/intlify/vue-i18n-next/pull/1525

Full Changelog: intlify/vue-i18n@v9.3.0...v9.4.0

`v9.3.0`

Compare Source

We are excited to announce the release of Vue I18n v9.3, finally !! This release includes some new features, bug fixes, improvements, and document fixes.

We had commited with 37 contributors. Thanks for your contributing ❤️

In the following, we introduce some of the new features:

🌟 Features

Node.js Dual packages (`cjs` / `mjs`)

We provide CommonJS and Native ESM dual module packages for Node.js. This supports both require and import for loading modules in Node.js.

feat: cjs/mjs file extension fully by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1147
feat: support ESM file extension by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1137
feat: node esm for message compiler by @kazupon in https://github.com/intlify/vue-i18n-next/pull/1460

JIT Style Compilation

Supports JIT (Just In Time) style compilation of message formats. This mean, removes the CSP limitation and allows for use in environments such as Service worker, Web worker, and Edge.

It mean also now supports the use-case where locale messages are dynamically retrieved from the backend via the API.

For more information, please see the docs

The performance of JIT-style compilation is close to that of conventional AOT (Ahead Of Time) style compilation, and you can improve the performance to nearly 3x with combination of JIT + AOT.

Below are the compile performance benchmark results for vue-i18n:

> node ./benchmark/index.mjs

compilation:

compile simple message x 396,898 ops/sec ±0.31% (98 runs sampled)
compile complex message x 60,036 ops/sec ±0.34% (99 runs sampled)

simple pattern on 1000 resources (AOT):

resolve time wit

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "" (UTC), 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.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/intlify/routing).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS40Mi40IiwidXBkYXRlZEluVmVyIjoiMzkuMjU3LjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbIlR5cGU6IERlcGVuZGVuY3kiXX0=-->

renovate bot added the Type: Dependency label Dec 2, 2024

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed Dec 8, 2024

renovate bot closed this Dec 8, 2024

renovate bot deleted the renovate/npm-vue-i18n-legacy-vulnerability branch December 8, 2024 19:01

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 8, 2024

renovate bot reopened this Dec 8, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from ddfea19 to 3f4ac72 Compare December 8, 2024 22:01

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 3f4ac72 to be5b346 Compare December 17, 2024 19:56

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v10 [security] Dec 17, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from be5b346 to be692fb Compare December 17, 2024 23:51

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v10 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 17, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from be692fb to a1f820f Compare December 22, 2024 18:57

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v10 [security] Dec 22, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from a1f820f to 5fff31c Compare December 22, 2024 21:29

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v10 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 22, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 5fff31c to 81760e2 Compare January 14, 2025 17:28

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 14, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 81760e2 to 1d9ba05 Compare January 15, 2025 00:00

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 15, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 1d9ba05 to dcef09d Compare January 23, 2025 17:03

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 23, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from dcef09d to 8b80aa8 Compare January 23, 2025 21:28

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 23, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 8b80aa8 to 209f31c Compare January 30, 2025 17:50

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 30, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 209f31c to c4fe81f Compare January 30, 2025 21:41

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 30, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from c4fe81f to 6af586a Compare February 9, 2025 13:34

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Feb 9, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 6af586a to 41ffc03 Compare February 9, 2025 17:57

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Feb 9, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 41ffc03 to 21735da Compare March 3, 2025 12:27

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Mar 3, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 21735da to 0441f25 Compare March 3, 2025 20:06

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Mar 3, 2025

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed Mar 7, 2025

renovate bot closed this Mar 7, 2025

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Mar 7, 2025

renovate bot reopened this Mar 7, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch 2 times, most recently from ff44329 to 2f5ce90 Compare March 11, 2025 12:26

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Mar 11, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 2f5ce90 to 6676144 Compare March 11, 2025 23:09

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Mar 11, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 6676144 to 98c6510 Compare March 13, 2025 15:19

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Mar 13, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 98c6510 to c54e1e2 Compare March 13, 2025 19:23

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Mar 13, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from c54e1e2 to 0d8d80d Compare March 17, 2025 16:46

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Mar 17, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 0d8d80d to cbf5fc6 Compare March 17, 2025 23:04

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Mar 17, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from cbf5fc6 to cc1d723 Compare April 1, 2025 13:09

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Apr 1, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from cc1d723 to 52c2475 Compare April 1, 2025 19:31

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Apr 1, 2025

chore(deps): update dependency vue-i18n-legacy to v11 [security]

8fc06e1

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 52c2475 to 8fc06e1 Compare April 24, 2025 08:52

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Apr 24, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

renovate bot commented Dec 2, 2024 •

edited

Loading

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

Are you sure you want to change the base?

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

Conversation

renovate bot commented Dec 2, 2024 • edited Loading

GitHub Vulnerability Alerts

Vulnerability type

Description

Reproduce (PoC)

Workarounds

References

Release Notes

What's Changed

🐛 Bug Fixes

⚡ Improvement Features

What's Changed

🔒 Security Fixes

What's Changed

🌟 Features

📝️ Documentations

What's Changed

⚡ Improvement Features

What's Changed

Deprecate Legacy API mode

Deprecate Custom Directive v-t

Drop tc and $tc for Legacy API mode

Vue I18n maintenance Status

❗ Breaking Changes

⚡ Improvement Features

🔒 Security Fixes

📝️ Documentations

👋 New Contributors

What's Changed

🐛 Bug Fixes

What's Changed

🔒 Security Fixes

What's Changed

🔒 Security Fixes

What's Changed

🐛 Bug Fixes

📝️ Documentations

New Contributors

What's Changed

🐛 Bug Fixes

📝️ Documentations

What's Changed

⚡ Improvement Features

📝️ Documentations

What's Changed

🐛 Bug Fixes

New Contributors

What's Changed

🐛 Bug Fixes

What's Changed

🔒 Security Fixes

What's Changed

🔒 Security Fixes

What's Changed

🐛 Bug Fixes

What's Changed

⚡ Improvement Features

What's Changed

🐛 Bug Fixes

What's Changed

⚠️ Deprecated Features

⚡ Improvement Features

📝️ Documentations

New Contributors

What's Changed

🐛 Bug Fixes

👕 Refactoring

What's Changed

🌟 Features

What's Changed

🐛 Bug Fixes

What's Changed

🌟 Features

New Contributors

What's Changed

🐛 Bug Fixes

renovate bot commented Dec 2, 2024 •

edited

Loading

Deprecate Custom Directive `v-t`

Drop `tc` and `$tc` for Legacy API mode