vscode: Can no longer find config file from 1.24.5+

Describe the bug

Yesterday the extension (1.24.4) worked.

Today it does not (1.24.5 and 1.24.6). These two version are not able to find the configuration file.

Nothing has changed since yesterday (same editor configs, same project config files, etc.).

Reproduction

Open VSCode and bring up the “Testing” sidebar.

Image

Output

[INFO 10:40:58 AM] [v1.24.6] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 10:40:59 AM] [API] Resolving configs: [REDACTED]/vite.config.ts
[INFO 10:40:59 AM] [API] Initiated ws connection via ws://localhost:53182
[INFO 10:40:59 AM] [API] Starting Vitest v3.2.3 ([REDACTED]/vite.config.ts) in the terminal: node C:/Users/[USER]/.vscode/extensions/vitest.explorer-1.24.6/dist/worker.js
[Error 10:41:04 AM] There were errors during config load.
[Error 10:41:04 AM] [Error Error] The extension could not connect to the terminal in 5 seconds. See the "vitest" terminal output for more details.
Error: The extension could not connect to the terminal in 5 seconds. See the "vitest" terminal output for more details.
	at Timeout._onTimeout (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:13:3802)
	at listOnTimeout (node:internal/timers:588:17)
	at process.processTimers (node:internal/timers:523:7)
[Error 10:41:06 AM] [Error Error] The extension could not load any config.
Error: The extension could not load any config.
    at kl (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:13:9918)
    at Li._defineTestProfiles (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:25:2314)
    at Li.defineTestProfiles (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:25:1701)
    at Li.activate (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:25:7158)
    at ME (c:\Users\[USER]\.vscode\extensions\vitest.explorer-1.24.6\dist\extension.js:25:662)
    at Wb.n (file:///c:/Users/[USER]/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:120:13382)
    at Wb.m (file:///c:/Users/[USER]/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:120:13345)
    at Wb.l (file:///c:/Users/[USER]/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:120:12801)

Extension Version

1.24.6

Vitest Version

3.2.3

Validations

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Reactions: 7
  • Comments: 24 (9 by maintainers)

Most upvoted comments

The default is now child_process again (since v1.26.0). Thank you for your reports, I will take a closer look at this terminal integration.

My extension was stuck in “Resolving vitest…” on Windows.

Downgrading the extension to 1.24.3 fixed it for me.

Yeah, as discussed in the discord, I’m going through the very same. I’m on OSX and the only thing that gets things working again is by turning the shell type back to old default, child process. I’ve tried all the shell configs above, and messed around with my node version etc too, but nothing else has done anything.