Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(README): fix typo in the README of vite-plugin-vue-i18n #45

Merged
merged 1 commit into from Sep 20, 2021
Merged

docs(README): fix typo in the README of vite-plugin-vue-i18n #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions packages/vite-plugin-vue-i18n/README.md
View file
Open in desktop
Expand Up @@ -218,7 +218,7 @@ vite-plugin-vue-i18n will automatically select and bundle Vue I18n build accordi

About details, See the [here](https://vue-i18n.intlify.dev/guide/advanced/optimization.html#improve-performance-and-reduce-bundle-size-with-runtime-build-only)

### For `petite-vue-ei18n`
### For `petite-vue-i18n`

vite-plugin-vue-i18n will automatically select and bundle `petite-vue-i18n` build according to the following vite behavior:

Expand Down Expand Up @@ -423,7 +423,7 @@ About details, See the below section
- **Type:** `boolean`
- **Default:** `false`

Whether to use the imporot name of `petite-vue-i18n` with the same import name as vue-i18n (`import { xxx } from ‘vue-i18n’`).
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 enhacement.

Expand Down