-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Nuxt/i18n v9.1.0 breaks Vitest code coverage #3238
Comments
I have no idea how this module could influence the coverage generation 🤔 Unfortunately I can't confirm this is caused by this module using the provided reproduction, even when removing Nuxt I18n, the generated coverage file seems to only contain |
It looks like I can't reproduce it well either… That's a shame ! However, as odd as it is, I can assure that upgrading the version to 9.1.0 actually breaks the coverage on my project here : https://github.com/antoinezanardi/werewolves-assistant-web-next/actions/runs/11915097536 Back to the reproduction, I think that StackBlitz as some issues with coverage reporters… Maybe running it local will be different ? |
I just tried it debugging the issue using the You're right that updating to |
Thanks a lot for your investigation. You're right, downgrading it after that won't resolve the issue. I had to rollback the |
Upgrading from 8.5.5 to 9.0.0 seems to cause this issue for me. |
Environment
Nuxt project info:
Reproduction
You can reproduce the bug with the StackBlitz here : https://stackblitz.com/edit/nuxt-starter-gpaujj?file=package.json
Run the following commands :
Describe the bug
When using Vitest to generate code coverage (with either
v8
oristanbul
), it appears that v9.1.0 introduces a bug that breaks the generated coverage files and their output.Observed Behavior:
coverage/final-coverage.json
contains only{}
, which is incorrect.Expected Behavior:
coverage/final-coverage.json
file should correctly represent the coverage data.Temporary Fix:
Reverting to v9.0.0 resolves the issue and restores normal functionality.
Additional context
You can also see that something's wrong one the PR that updates the package on a larger project of mine, with this job : https://github.com/antoinezanardi/werewolves-assistant-web-next/actions/runs/11915097536
(It checks that the coverage results are not empty).
Logs
The text was updated successfully, but these errors were encountered: