Ari Perkkiö

I'm not actually sure how this works right now. My guess is that runner in browser doesn't see worker's scope and cannot collect the coverage from `window.__VITEST_COVERAGE__` object. @DenizUgur could...

I can reproduce the issue now. However when debugging anything browser-mode related with locally linked Vitest, whole test run freezes completely. Need to figure out that one first. This kind...

Coverage collection for browser's Workers is not supported. I don't think this has been looked into before as there as been no feature requests for it. Istanbul instrumented files collect...

At the moment this is not being worked on. I cannot give any time estimates right now but at some point we should try to implement this. This won't be...

I'm not yet sure how exactly the implementation would go. I would need to do some proof-of-concept work before to see the bigger picture. But basically the idea would be:...

Now that we have V8 coverage for browser mode, I would have expected worker's coverage to be automatically collected from there. I'm not sure if it's even possible to control...

> Blocking a main thread for such a long time should be avoided in general. This is actually blocking the test runner thread, and prevents it from receiving update from...

> Locally everything works just fine for me, but in CI something is failing, and I have no clue what or why. @manuel3108 aren't your tests also blocking the thread...

> also mentioned that this was introduced at a specific, non major version number. This kind of bugs shouldn't be introduced no matter what the version number is. @hi-ogawa this...

This report contains two issues: 1. Something (nuxt ?) is importing files that are not being tested. Node's V8 coverage includes every file that is loaded via Node. The repro...