-
-
Notifications
You must be signed in to change notification settings - Fork 334
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.
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
v10.0.1 throws error at build time (Vite/Nuxt) #1946
Comments
Can you check what version If that doesn't resolve it, a minimal reproduction would be very helpful in debugging this further 🙏 |
Deleting the lockfile and reinstalling packages did not solve it, but changed the error message to a different one:
I will try to create a reproduction later 👍 @intlify/core-base version (same before reinstall and after):
|
Ok, after adding "overrides": {
"@intlify/core-base": "^10.0.1"
} to my
I get a third, also different error message 😄
|
Ok, solved it. "overrides": {
"vue-i18n": "^10.0.1"
} to the The issue seems to be in the
|
Oh I see you're using |
Ah nice, thanks! Then I will wait for |
I'm also getting this. Unfortunately, the fix proposed by @Anton-Plagemann didn't work.
FWIW the issue started when moving to a monorepo structure with Lerna, although I don't think it's related. |
Hi @DamageESP, {
"dependencies": {
"vue-i18n": "^9.14.0"
},
"devDependencies": {
"@intlify/unplugin-vue-i18n": "^4.0.0"
}
} |
Thanks for the suggestion @Anton-Plagemann, but the solution was different (and simpler). As @BobbieGoede very well pointed out, - "@nuxtjs/i18n": "next",
+ "@nuxtjs/i18n": "^8.0.0", This resolved all my problems, of course after running a clean install (deleted I hope this helps clean up your Note: It's interesting though that we have a broken version of the library in |
Downgrading to an older version of
Perhaps related to the fact that |
@StijnCoolen
You should not use any other combination. If you're using If you are using compatible versions, make sure these are up to date and refresh/remove your lock files to force the installation of correct sub-dependencies (these errors seem to hint at this being the issue). |
@BobbieGoede thanks for thinking with me! Installing only
|
That's odd, can you try doing the same but installing the latest nightly release channel instead ( |
I fixed the
All 3 were required to stop the error from appearing at build time or runtime |
Reporting a bug?
Got a build error after upgrading to v10.
Expected behavior
Should build without errors
Reproduction
The error seems straighforward, if you need a reproduction let me know and I will try to create one.
System Info
Screenshot
Additional context
Validations
The text was updated successfully, but these errors were encountered: