improvement: vue-i18n re-packaging #222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have optimized the package configuration for vue-i18n.
This PR solves the following problems
The vue-i18n package has been reconfigured so that the modules provided are now runtime only, as well as the compiler and runtime like Vue 3.
The fact that vue-i18n only provides runtime means that precompilation of locale messages is required.
The most common use case for i18n is to create large applications. In that case, today we use a bundler like webpack to create the application.
i18n resources such as locale messages use plain text format like
.json.These i18n resources will now need to use the loader / plugin provided by the intlify project for each bundler, such as vue-i18n-loader.
as my next action, I will be to extend the following loader / plugin.