Vitest process starts properly at initial launch, but fails to refresh (Yarn PnP, Monorepo)

[JunyeongChoi0]

I am using the VSCode Vitest extension in a monorepo with Yarn PnP. The initial execution of the Vitest process works correctly, but there is an issue with the refresh not working properly.

One strange thing in the attached error log is that during the initial execution, Vitest runs with several parameters like /Users/choejun-yeong/.nvm/versions/node/v20.16.0/bin/node --require /Users/choejun-yeong/3o3/3o3_service/.pnp.cjs --experimental-loader file:///Users/choejun-yeong/3o3/3o3_service/.pnp.loader.mjs, but during the refresh, it logs as /Users/choejun-yeong/.nvm/versions/node/v20.16.0/bin/node with no parameters at all.

Before reporting as an issue, I wanted to check if there is a known solution for this.

And sorry for cannot providing a repro because this is private repo code.

Here is the attached error message:

[INFO 오전 12:47:04] [v1.6.0] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 오전 12:47:04] [API] Running Vitest vpnp (3o3_service/vitest.workspace.ts) with [email protected]: /Users/choejun-yeong/.nvm/versions/node/v20.16.0/bin/node --require /Users/choejun-yeong/3o3/3o3_service/.pnp.cjs --experimental-loader file:///Users/choejun-yeong/3o3/3o3_service/.pnp.loader.mjs
[INFO 오전 12:47:05] [API] Vitest vpnp (3o3_service/vitest.workspace.ts) child process 41338 created
[INFO 오전 12:47:05] [VSCODE] Watching 3o3_service with pattern **/*
[INFO 오전 12:47:24] [API] Vitest process 41338 closed successfully
[INFO 오전 12:47:24] [API] Running Vitest v2.1.2 (3o3_service/vitest.workspace.ts) with [email protected]: /Users/choejun-yeong/.nvm/versions/node/v20.16.0/bin/node 
[Error 오전 12:47:24] [API] Failed to refresh Vitest [Error Error] Vitest failed to start: 
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/choejun-yeong/3o3/3o3_service/.yarn/__virtual__/vitest-virtual-d765642456/0/cache/vitest-npm-2.1.2-6430425a96-3a331a1049.zip/node_modules/vitest/dist/node.js' imported from /Users/choejun-yeong/.vscode/extensions/vitest.explorer-1.6.0/dist/worker.js
    at finalizeResolution (node:internal/modules/esm/resolve:265:11)
    at moduleResolve (node:internal/modules/esm/resolve:933:10)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12)
    at To (/Users/choejun-yeong/.vscode/extensions/vitest.explorer-1.6.0/dist/worker.js:20:7180)
Error: Vitest failed to start: 
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/choejun-yeong/3o3/3o3_service/.yarn/__virtual__/vitest-virtual-d765642456/0/cache/vitest-npm-2.1.2-6430425a96-3a331a1049.zip/node_modules/vitest/dist/node.js' imported from /Users/choejun-yeong/.vscode/extensions/vitest.explorer-1.6.0/dist/worker.js
    at finalizeResolution (node:internal/modules/esm/resolve:265:11)
    at moduleResolve (node:internal/modules/esm/resolve:933:10)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12)
    at To (/Users/choejun-yeong/.vscode/extensions/vitest.explorer-1.6.0/dist/worker.js:20:7180)
    at ChildProcess.p (/Users/choejun-yeong/.vscode/extensions/vitest.explorer-1.6.0/dist/extension.js:19:3538)
    at ChildProcess.emit (node:events:519:28)
    at emit (node:internal/child_process:951:14)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

[JunyeongChoi0]

Seems like not problem of vitest or vitest extension. require.resolve() returns different value between initial load and second load - initial, error so take pnp approach but second, success - I will taking a deeper look in it

[JunyeongChoi0]

Closing, because this seems to bug. filed issue #507