Failed to load config on the console

[SiKreuz]

Describe the bug

When the extension is installed, it eventually blocks runs on the console of vite and vitest. The following error message is appearing on the screen. Tests are passing perfectly in the extension. I cannot run tests on the console when the extension is enabled.

The issue doesn't happen right away. I think it's happening on changing branches and installing dependencies but I cannot tell for sure. But it starts quite soon after opening vscode and doesn't go away until a full restart or uninstalling the extension.

bun run serve
$ vite
failed to load config from /Users/simon/Documents/OneTutor/repos/OneTutor/apps/frontend/vite.config.ts
error when starting dev server:
Error: The service was stopped
    at /Users/simon/Documents/OneTutor/repos/OneTutor/node_modules/esbuild/lib/main.js:947:34
    at responseCallbacks.<computed> (/Users/simon/Documents/OneTutor/repos/OneTutor/node_modules/esbuild/lib/main.js:601:9)
    at Socket.afterClose (/Users/simon/Documents/OneTutor/repos/OneTutor/node_modules/esbuild/lib/main.js:592:28)
    at Socket.emit (node:events:519:35)
    at endReadableNT (node:internal/streams/readable:1701:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
error: script "serve" exited with code 1

Reproduction

Setup: Monorepo with three projects, two of them having tests

1. switch branches
2. install dependencies (we are using bun as package manager, but not runtime)
3. Try to run vitest run or vite on the console.

Output

I cannot paste the output as it is too long. Just posting the start. There seems to be no error. Also testing with the extension is not the issue...


[INFO 10:25:24 AM] [v1.26.4] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 10:25:24 AM] [API] Resolving configs: shared/vitest.config.ts, frontend/vite.config.ts, backend/vitest.config.ts
[INFO 10:25:24 AM] [API] Running Vitest v3.2.4 (shared/vitest.config.ts) with "/opt/homebrew/bin/node /Users/simon/.vscode/extensions/vitest.explorer-1.26.4/dist/worker.js"
[INFO 10:25:24 AM] [API] Running Vitest v3.2.4 (frontend/vite.config.ts) with "/opt/homebrew/bin/node /Users/simon/.vscode/extensions/vitest.explorer-1.26.4/dist/worker.js"
[INFO 10:25:24 AM] [API] Running Vitest v3.2.4 (backend/vitest.config.ts) with "/opt/homebrew/bin/node /Users/simon/.vscode/extensions/vitest.explorer-1.26.4/dist/worker.js"
[INFO 10:25:24 AM] [API] Watching vitest.config.ts
[INFO 10:25:24 AM] [VSCODE] Watching shared with pattern **/*
[INFO 10:25:24 AM] [API] Watching vite.config.ts
[INFO 10:25:24 AM] [VSCODE] Watching frontend with pattern **/*
[INFO 10:25:24 AM] [API] Watching vitest.config.ts
[INFO 10:25:24 AM] [VSCODE] Watching backend with pattern **/*
[INFO 10:25:27 AM] Running 1 file(s):

Extension Version

1.26.4

Vitest Version

3.2.4

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.

[jpremill]

I have a similar problem where now what happens is that it looks for my exact project directory, but in the C drive instead of the F drive. I tried closing the directory in vscode ,renaming the directory, then opening it again, and it is still pointing to C instead of F. I have yet to find a way to help vscode or vitest find the correct info for the workspace location

[SiKreuz]

It seems that bun v1.3 did fix this for me. Cannot reproduce it anymore