Supporting `vitest` tracking issue

Question

Supporting `vitest` tracking issue

marvinhagemeister opened this issue a month ago · comments

Marvin Hagemeister commented a month ago

This is an issue to track the progress on getting the vitest test runner to work. I'm currently using the test suite from urql to check our progress.

~~Web MessagePort not converted to worker_thread MessagePort #23828~~
Node globals missing in vm.runInThisConext #23852
TTY test result reporter not working because of this check https://github.com/vitest-dev/vitest/blob/main/packages/vitest/src/utils/env.ts#L1
- ~~signal-exit is used under the hood. It's likely that this issue causes CTRL+C to not work: #22892~~
Test run doesn't seem to complete