fix: improve error handling for vue-i18n v9 invalid message syntax #1522
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
❌ Deploy Preview for nuxt-i18n-v8 failed.
|
|
|
|
The v8 docs build is failing, but CI is passing. So I will merge them (Later I will solve it). |
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.
resolve #1519
Invalid message syntax in vue-i18n v9 (e.g.
@unescaped with literal intrepolation), error handling was not handled properly in@intlify/unplugin-vue-i18n(@intlify/bundle-utils), resulting in a 500 error in nuxt, we can understand it difficult to know where message was.That issue has been already fixed in the following PR so that we will upgrade
@intlify/unplugin-vue-i18n.related issue: intlify/bundle-tools#164
related PR: intlify/bundle-tools#173