@intlify/unplugin-vue-i18n 7.0.0-beta.1 → 11.0.0-beta.3

package/README.md

@@ -6,6 +6,8 @@
 
 unplugin for Vue I18n
 
+<!-- eslint-disable markdown/no-missing-label-refs -->
+
 ## 🌟 Features
 
 - i18n resource pre-compilation
@@ -59,25 +61,6 @@ module.exports = {
 
 <br></details>
 
-<details>
-<summary>Rspack</summary><br>
-
-```ts
-const VueI18nPlugin = require('@intlify/unplugin-vue-i18n/rspack')
-
-// rspack.config.js
-module.exports = {
-  /* ... */
-  plugins: [
-    VueI18nPlugin({
-      /* options */
-    })
-  ]
-}
-```
-
-<br></details>
-
 <details>
 <summary>Nuxt</summary><br>
 
@@ -288,7 +271,7 @@ About details, See the [here](https://vue-i18n.intlify.dev/guide/advanced/optimi
 
   A [picomatch](https://github.com/micromatch/picomatch) pattern, or array of patterns, you can specify a path to pre-compile i18n resources files. The extensions of i18n resources to be precompiled are as follows:
 
-  ```
+  ```md
   - json
   - json5
   - yaml
@@ -299,17 +282,11 @@ About details, See the [here](https://vue-i18n.intlify.dev/guide/advanced/optimi
 
   If nothing is specified for this option, i.e. `undefined`, nothing is done to the resource in the above format.
 
-> [!WARNING]
->
-> `json` resources matches this option, it will be handled **before the internal json plugin of bundler, and will not be processed afterwards**, else the option doesn't match, the bundler side will handle.
+> [!WARNING] > `json` resources matches this option, it will be handled **before the internal json plugin of bundler, and will not be processed afterwards**, else the option doesn't match, the bundler side will handle.
 
-> [!WARNING]
->
-> `yaml` resources don't support multi documentation with `|`, alias with `&` and `*`, tags with `! `, `@`, etc. Only simple data structures.
+> [!WARNING] > `yaml` resources don't support multi documentation with `|`, alias with `&` and `*`, tags with `! `, `@`, etc. Only simple data structures.
 
-> [!WARNING]
->
-> `js` and `ts` resources are set **simple export (`export default`) as locale messages object, as default**.
+> [!WARNING] > `js` and `ts` resources are set **simple export (`export default`) as locale messages object, as default**.
 
 ```js
 export default {
@@ -328,22 +305,22 @@ If you need to use programmatically dynamic resource construction, you would be
 - **Type:** `string`
 - **Default:** `'vue-i18n'`
 
-> [!NOTE]
-> This options is supported from v5.1.0, and works with vue-i18n v10 and later.
+  > [!NOTE]
+  > This options is supported from v5.1.0, and works with vue-i18n v10 and later.
 
-Bundle target vue-i18n module. You can specify either `‘vue-i18n’` or `‘petite-vue-i18n’`.
+  Bundle target vue-i18n module. You can specify either `‘vue-i18n’` or `‘petite-vue-i18n’`.
 
-The default is `'vue-i18n'`, and the following installed in node_modules will be bundled.
+  The default is `'vue-i18n'`, and the following installed in node_modules will be bundled.
 
-- development: `vue-i18n.esm-bundler.js`
-- production: `vue-i18n.runtime.esm-bundler.js`
+  - development: `vue-i18n.esm-bundler.js`
+  - production: `vue-i18n.runtime.esm-bundler.js`
 
-In the case of `‘petite-vue-i18n’`, the following installed in node_modules will be bundled.
+  In the case of `‘petite-vue-i18n’`, the following installed in node_modules will be bundled.
 
-- development: `petite-vue-i18n.esm-bundler.js`
-- production: `petite-vue-i18n.runtime.esm-bundler.js`
+  - development: `petite-vue-i18n.esm-bundler.js`
+  - production: `petite-vue-i18n.runtime.esm-bundler.js`
 
-If you are using petite-vue-i18n, you will need to set this value.
+  If you are using petite-vue-i18n, you will need to set this value.
 
 ### `strictMessage`
 
@@ -385,7 +362,7 @@ If you are using petite-vue-i18n, you will need to set this value.
   }
   ```
 
-  If you fetch some resources from the backend, the data **must be pre-compiled** for production. example is [here](https://github.com/intlify/vue-i18n-next/tree/master/examples/backend).
+  If you fetch some resources from the backend, the data **must be pre-compiled** for production. exmaple is [here](https://github.com/intlify/vue-i18n-next/tree/master/examples/backend).
 
 ### `jitCompilation`
 
@@ -393,15 +370,15 @@ If you are using petite-vue-i18n, you will need to set this value.
 - **Default:** `true`
 
 > [!IMPORTANT]
-> 'jitCompilation' option is deprecated in v5.
+> 'jitCompilation' option is deprected in v5.
 > This option will be supported with vue-i18n until v9 latest version.
 
-Whether locale messages should be compiled by JIT (Just in Time) compilation with vue-i18n's message compiler.
+Whether locale mesages should be compiled by JIT (Just in Time) compilation with vue-i18n's message compiler.
 
-JIT compilation has been supported since vue-i18n v9.3. This means that since v9 was released until now, the message compiler compiles to executable JavaScript code, however it did not work in the CSP environment. Also, since this was an AOT (Ahead of Time) compilation, it was not possible to dynamically retrieve locale messages from the back-end Database and compose locale messages with programmatic.
+JIT compilation has been supported since vue-i18n v9.3. This means that since v9 was released until now, the message compiler compiles to executable JavaScript code, however it did not work in the CSP environment. Also, since this was an AOT (Ahead of Time) compilation, it was not possible to dynamically retrieve locale messages from the back-end Database and compose locale mesages with programatic.
 
 > [!WARNING]
-> Enabling JIT compilation causes the message compiler to generate AST objects for locale messages instead of JavaScript code. If you pre-compile locale messages with a tool such as the [Intlify CLI](https://github.com/intlify/cli) and import them dynamically, you need to rebuild that resource.
+> Enabling JIT compilation causes the message compiler to generate AST objects for locale mesages instead of JavaScript code. If you pre-compile locale messages with a tool such as the [Intlify CLI](https://github.com/intlify/cli) and import them dynamically, you need to rebuild that resource.
 
 About JIT compilation, See [here](https://vue-i18n.intlify.dev/guide/advanced/optimization.html#jit-compilation)
 
@@ -440,10 +417,9 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   Whether or not to automatically use Vue I18n **runtime-only** in production build, set `vue-i18n.runtime.esm-bundler.js` in the `vue-i18n` field of bundler config, the below:
 
-  ```
+  ```md
   - vite config: `resolve.alias`
   - webpack config: `resolve.alias`
-  - rspack config: `resolve.alias`
   ```
 
   If `false` is specified, Vue I18n (vue-i18n) package.json `module` field will be used.
@@ -459,9 +435,6 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   For more details, See [here](https://vue-i18n.intlify.dev/guide/advanced/optimization.html#reduce-bundle-size-with-feature-build-flags)
 
-> [!CAUTION]
-> This option will be removed in v7
-
 ### `fullInstall`
 
 - **Type:** `boolean`
@@ -469,7 +442,7 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   Whether to install the full set of APIs, components, etc. provided by Vue I18n. By default, all of them will be installed.
 
-  If `false` is specified, **build-in components and directive will not be installed in vue and will be tree-shaken.**
+  If `false` is specified, **buld-in components and directive will not be installed in vue and will be tree-shaken.**
 
   For more details, See [here](https://vue-i18n.intlify.dev/guide/advanced/optimization.html#reduce-bundle-size-with-feature-build-flags)
 
@@ -539,7 +512,7 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   `defaultSFCLang` must have one of the following values:
 
-  ```
+  ```md
   - json
   - json5
   - yaml
@@ -626,10 +599,8 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   This option that to use i18n custom blocks in `vue-class-component`.
 
-> [!IMPORTANT]
->
-> `useClassComponent` option is deprecated in v5.
-> This option will be supported with vue-i18n until v9 latest version.
+  > [!IMPORTANT] > `useClassComponent` option is deprecated in v5.
+  > This option will be supported with vue-i18n until v9 latest version.
 
 ### `onlyLocales`
 
@@ -645,12 +616,10 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   Whether to use the import name of `petite-vue-i18n` with the same import name as vue-i18n (`import { xxx } from 'vue-i18n'`).
 
-  This option allows a smooth migration from `petite-vue-i18n` to `vue-i18n` and allows progressive enhancement.
+  This option allows a smooth migration from `petite-vue-i18n` to `vue-i18n` and allows progressive enhacement.
 
-> [!IMPORTANT]
->
-> `useVueI18nImportName` option is deprecated in v5.
-> This option will be supported with vue-i18n until v9 latest version.
+  > [!IMPORTANT] > `useVueI18nImportName` option is deprecated in v5.
+  > This option will be supported with vue-i18n until v9 latest version.
 
 ### `optimizeTranslationDirective`
 
@@ -661,8 +630,8 @@ If do you will use this option, you need to enable `jitCompilation` option.
 
   If you want to put it manually, you can specify the signature of the translation function as a string or a string array.
 
-> [!WARNING]
-> About for manually signature, see the details [vue-i18n-extensions API docs](https://github.com/intlify/vue-i18n-extensions/blob/next/docs/%40intlify/vue-i18n-extensions-api.md#translationsignatures) and [usecase from vue-i18n-extensions PR](https://github.com/intlify/vue-i18n-extensions/pull/217/files#diff-3fb9543f91e011d4b0dc9beff44082fe1a99c9eab70c1afab23c3c34352b7c38R121-R200)
+  > [!WARNING]
+  > About for manually signature, see the details [vue-i18n-extensions API docs](https://github.com/intlify/vue-i18n-extensions/blob/next/docs/%40intlify/vue-i18n-extensions-api.md#translationsignatures) and [usecase from vue-i18n-extensions PR](https://github.com/intlify/vue-i18n-extensions/pull/217/files#diff-3fb9543f91e011d4b0dc9beff44082fe1a99c9eab70c1afab23c3c34352b7c38R121-R200)
 
 ### `transformI18nBlock`
 
@@ -714,8 +683,8 @@ If do you will use this option, you need to enable `jitCompilation` option.
   </i18n>
   ```
 
-> [!IMPORTANT]
-> The function **must** return a string or the build will fail.
+  > [!IMPORTANT]
+  > The function **must** return a string or the build will fail.
 
 ## 📜 Changelog
 
@@ -724,3 +693,5 @@ Details changes for each release are documented in the [CHANGELOG.md](https://gi
 ## ©️ License
 
 [MIT](http://opensource.org/licenses/MIT)
+
+<!-- eslint-enable markdown/no-missing-label-refs -->