Ari Perkkiö
Ari Perkkiö
I'm not sure how this could be implemented. I thought `tsconfig.json`'s `paths` would do this automatically, but looks like relative imports are not remapped via `paths`. So something like this...
Setup file is run only once for the test runner due to `--no-isolate`. A single test runner is spawned due to `--no-file-parallelism`. The fact that there is a failing test...
How is that related? You need isolation for tests that are manipulating the DOM. That setup is not using `*each` hooks at all. The problem in this issue to me...
> this mode also breaks `@testing-library/dom` > It's (should be) [called](https://testing-library.com/docs/preact-testing-library/api/#cleanup) internally by `@testing-library/react`. Oh right, you are using `@testing-library/react`, not `@testing-library/dom`. The issue is reported in wrong Github project....
Could you try to narrow down the reproduction case to a smaller one? Ideally to a setup with just a one source file and one test file. In Vitest's test...
Maybe this comes up when multiple test files are testing a single source file. In Vitest's internal test cases I don't think we have those that much.
Can this be reproduced with latest Vitest `1.4.0`? `threads: false` was removed before v1.
It would be great if someone could set up a **minimal** reproduction case. That's the first step to fix this.
Continues in https://github.com/vitest-dev/vitest/issues/6736
RSS feed support is not something we are prioritizing right now. But we will accept a pull request for this, if proposed changes are not too complex.