Watch mode skips all tests in a clean SvelteKit project

[sjoerdvanBommel]

Describe the bug
The VSCode Vitest plugin fails to execute any unit tests when running in watch mode (for example in a clean SvelteKit project).

To Reproduce
Steps to reproduce the behavior:

1. Create a clean TypeScript skeleton SvelteKit project with all options included: npm create svelte@latest test-app
2. cd test-app
3. npm i
4. (Optional) Run the tests with the default runner. This works as expected
   
5. Run the tests using watch mode
   
6. All tests are skipped for some reason. At the top and bottom, it mentions "0/0 tests passed (0.00%)" and "0/0 passed (0%, all skipped)"
   

Expected behavior
Similar behavior to when I run the tests without watch mode, but instead affected tests should be re-run.

Environment

(Paste info.txt content generated by the example project)

• OS: Windows 11 (OS build 22621.1848)
• VSCode version: 1.80.0
• Vitest version: ^0.32.2
• Vitest plugin version: v0.2.42

Let me know if anyone is able to reproduce this behavior. Thanks in advance! :)

[sjoerdvanBommel]

Two more points:

• I disabled all other VSCode extensions
• Once watch mode is running (it does run, it just skips all tests), starting any of the other tests does not trigger anything. You have to manually stop watch mode before you can run any tests via the plugin. You can do this by clicking the button below
  

[sjoerdvanBommel]

Couldn't find a related issue before, but found one now: #44
It seems to be broken since [email protected]. The tests run as expected until [email protected]
At least there is a workaround for now :) Edit: It seemed to work as expected after downgrading, but now watch mode only runs the tests once and doesn't react to any changes

[mcavigelli]

Let me know if anyone is able to reproduce this behavior. Thanks in advance! :)

We are using vitest plugin 0.2.42, vitest 0.33.0, vite 4.4.3 and VSCode 1.80.0 on windows.
We have the same behaviour. It can easily be reproduced by setting up a project as in the vitest repository in the folder https://github.com/vitest-dev/vitest/tree/main/examples/basic.

[callmeberzerker]

I have the same issue on Windows 11.

[sheremet-va]

This should be fixed in pre-release 0.5.0 and higher. Note that the extension now requires Vitest 1.4.0 or higher.