Version 1.24.7 stuck at "Resolving Vitest..."

[waypar]

Describe the bug

When I have v1.24.7 installed it doesn't work, it gets stuck at "Resolving Vitest..." in the test explorer window.

v1.24.6 works.

Reproduction

Install v1.24.7. Reload window If I switch from 1.24.6 to 1.24.7 it seems to work, but I don't know if there is some sort of caching. Reload window breaks it again. The only commit added c6c2b73cf84a30b675a25848bf7e32f4fd24fc7f seems to be doing web socket startup stuff, so I'm guessing an issue there. I have 2 folders with individual vitest configs.

Output

[INFO 21:22:37] [v1.24.7] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 21:22:38] [API] Resolving configs: xxx/vite.config.ts, xxx2/vitest.config.ts

Extension Version

1.24.7

Vitest Version

vitest/3.2.3 darwin-arm64 node-v22.16.0

Validations

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

[blshort43]

I'm also experiencing this with version 1.26.0, in VSCode. Installing version 1.24.6 fixes the issue.

[lukasjelonek]

Same for me. 1.26.0, 1.24.7 are stuck in "Resolving configs" step. 1.24.6 works.

[waypar]

I continue to have this issue in 1.26.0 as well

[jefflundberg]

1.26.3 still has this issue. I reverted to 1.24.6 for now.

Update 8/25/2025

1.28.2 still has the issue. I'm still using 1.24.6

[dippas]

for me is the v1.24.4 that works, I'm using insiders version

[lukasjelonek]

Is there some way to debug the extension? The problem still exists for me in 1.30.0 with vitest/3.2.4 darwin-arm64 node-v22.17.0

Is it possible that this is a mac os related problem, as @waypar also mentioned mac os in the opening message?

[antsfiles]

Similar for me (in Nx mono repo).. or if it works, the tree does not show correctly errors from roots branches.. Plus the amount of RAM used by the extension, and that sometimes the test pass in VSCode but not in command line... I'm thinking to switch back to Jest.

[lukasjelonek]

With the update to vitest 4 even the old versions got stuck indefinitely loading the test list. So I assumed that I need to update the extension to the latest version and to investigate whether the problem may come from my settings. And I found a non-default configuration. For some now unknown reason the configuration of Vitest: Shell Type was set to terminal instead of the default child_process. Resetting it to the default fixed the problem for me with the latest versions of the extension and vitest 4. I did not check for older versions.

So, at least for me, the problem existed not with the extension in general, but only with the terminal Shell type ingetration of the extension.