Plugin fails on startup with exit code 0

[CarsonTolleshaug]

Describe the bug

After installing the plugin, vscode reports that it cannot start the plugin because of an error. This same message is shown every time the project is loaded in vscode, and tests will not run. The error message shown looks like this:

Clicking "See Error" shows the following output:

[INFO 4:43:45 PM] [v1.6.6] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 4:43:46 PM] [API] Running Vitest v2.1.2 (superusersearch-svelte/vite.config.ts) with Node.js@v20.14.0: C:\Program Files (x86)\Nodist\bin\node.EXE 
[Error 4:43:46 PM] [Error Error] Vitest process exited with code 0
Error: Vitest process exited with code 0
	at ChildProcess.E (c:\Users\[REDACTED]\.vscode\extensions\vitest.explorer-1.6.6\dist\extension.js:21:177)
	at ChildProcess.emit (node:events:519:28)
	at ChildProcess._handle.onexit (node:internal/child_process:294:12)

Reproduction

The error seems to be hardware specific. I've never been able to run this extension, but my colleague was able to up until he upgraded to the same type of laptop as me (Dell Precision 5690). OS does not seem to be a factor either as he has Windows 11 on his new machine and I have Windows 10 and the same issue happens for both of us. Other colleagues with different hardware do not experience this issue.

It's worth noting that this model of laptop contains a dedicated GPU, where the others do not, so I'm wondering if this might be some sort of hardware acceleration issue.

I apologize for not being able to link to a repro due to the circumstances, I hope you understand.

To reiterate hardware specs:

• Windows 10 or 11
• Dell Precision 5690

Other potentially useful info:

• VS Code Version 1.95.1
• Vitest version 2.0.5
• Using Vitest in a SvelteKit project
• Using nodist to handle node version switching, currently set to version 20.14.0
• Other Vitest extensions do not have the same issue. Right now I'm using Vitest Runner for VSCode that actually work though it does not provide a graphical UI

Output

[INFO 4:43:45 PM] [v1.6.6] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 4:43:46 PM] [API] Running Vitest v2.1.2 (superusersearch-svelte/vite.config.ts) with Node.js@v20.14.0: C:\Program Files (x86)\Nodist\bin\node.EXE 
[Error 4:43:46 PM] [Error Error] Vitest process exited with code 0
Error: Vitest process exited with code 0
	at ChildProcess.E (c:\Users\[REDACTED]\.vscode\extensions\vitest.explorer-1.6.6\dist\extension.js:21:177)
	at ChildProcess.emit (node:events:519:28)
	at ChildProcess._handle.onexit (node:internal/child_process:294:12)

Version

1.6.6

Validations

• Check that you are using the latest version of the extension
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[JustinSometimesWrong]

Yep same error I see:

[INFO 7:12:27 AM] [v1.6.6] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 7:12:28 AM] [API] Running Vitest v2.1.2 ([REDACTED]/vite.config.ts) with Node.js@v20.10.0: C:\Program Files (x86)\Nodist\bin\node.EXE 
[Error 7:12:31 AM] [Error Error] Vitest process exited with code 0
Error: Vitest process exited with code 0
    at ChildProcess.E (c:\Users\[REDACTED]\.vscode\extensions\vitest.explorer-1.6.6\dist\extension.js:21:177)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess.emit (node:domain:488:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:294:12)

Tests are not visible in Test Explorer. No graphical widgets in the code editor to run the tests.