-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Vitest: Error: Missing "./messages" export in "@intlify/vite-plugin-vue-i18n" package #145
Comments
Thank you for your reporting! Unfortunately, I could not reproduce this issue 😞 |
I have the same issue with It can be reproduced by using the latest version of |
Same for me after updating
System Info
|
Got the same issue with the following dependencies I've created a minimum reproduction repository @kazupon I used pnpm, but the issue also happens with npm & yarn |
Thanks! |
These changes and the latest release do not fix the problem I have a problem with building the project too. it said:
|
Not sure what I'm doing wrong
Provided repro from @marekvospel is failing too after packages update to the latest: https://github.com/marekvospel/vitest-vite-plugin-vue-i18n |
Updated @kazupon the error is still present |
Yeah, Unfortunately, I could not still resolve this issue 😞 I recognize that the virtual module is automatically externalized in SSR. |
That seems to be a bug of Vite SSR ref: github issues on vite |
@kazupon vitejs/vite#9405 was merged. After updating vite to |
Thank you for your taking the time to let us know! |
@mHooshdar did figure this out? I was only able to get this working by specifying |
Reporting a bug?
I use
@intlify/vite-plugin-vue-i18n
to load my translation files.When I run Vitest, im getting the following error:
When I run
vite
orvite build
, everything works as expected.Expected behavior
The tests are using my translations.
Reproduction
vite.config.ts
tests/unit/setup.ts
@/i18n.ts
Issue Package
vite-plugin-vue-i18n
System Info
Screenshot
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: