Skip to content
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

Fix dynamic imports issue in core-frontend's vitest v8 coverage run #7711

Open
hl662 opened this issue Feb 17, 2025 · 0 comments
Open

Fix dynamic imports issue in core-frontend's vitest v8 coverage run #7711

hl662 opened this issue Feb 17, 2025 · 0 comments
Labels
buildology Issues related to process, tooling or CI/CD pipelines

Comments

@hl662
Copy link
Contributor

hl662 commented Feb 17, 2025

After #7340 and #7710, vitest's browser API is not playing nicely with their v8 coverage reporter, it's having issues with importing:

TypeError: Failed to fetch dynamically imported module: http://localhost:63315/@id/@vitest/coverage-v8/browser?import

One guess I have is Vite's build output is not creating the right filename for the compiled coverage-v8/browser.

In the meantime, we had to disable coverage reporting for core-frontend (other non-browser packages using vitest are fine).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
buildology Issues related to process, tooling or CI/CD pipelines
Projects
None yet
Development

No branches or pull requests

1 participant