Ari Perkkiö
Ari Perkkiö
Oh wow, does Node `22.11` fix this? Can't crash locally with that. `22.10` keeps crashing. Edit: Nope, it's much more stable but crashes after couple of minutes of re-running `test/core`...
Is this duplicate of https://github.com/vitest-dev/vitest/issues/5277?
Though global setup is executed in the main thread. Maybe we could do something like ```ts const cwd = process.cwd() process.chdir(dirname()) await import() process.chdir(cwd) ``` But would this just cause...
The reproduction works fine in jsdom and chrome+browser mode. Both throw `WrongDocumentError` as expected.
As it works on jsdom and browser mode, but not on happy-dom, I would say that this is an issue on their side. Vitest itself doesn't do anything related to...
V8 coverage uses source maps too. If a compiler adds code during transform, and includes it in source maps, coverage tools will show it in the report. Generated code should...
Maybe after https://github.com/vitest-dev/vitest/pull/7069 this could be solved
ugh this is not present on Node 18 
Vite 7 will drop Node 18 support so we can do this at the same time.
Vitest 4 will support Vite `6.0.0` which supports Node 18 too. Let's wait a year for this.