[Windows] Hangs at "Resolving Vitest..." forever

[Nithanim-Work]

Describe the bug

Using this extension v0.5.6 just shows "Resolving Vitest..." in the "Testing" tab of VS Code forever. We are using yarn with the pnp structure.

I tried debugging it (using latest master dad5884, sorry) and finally traced it back to https://github.com/vitest-dev/vscode/blob/main/src/api.ts#L276

I am not sure how this works but somehow the case is not handled where node does something (and exits?) but not starting any messaging. Capturing the stderr reveals the following:

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:131:11)
    at defaultLoad (node:internal/modules/esm/load:82:3)
    at nextLoad (node:internal/modules/esm/loader:163:28)
    at ESMLoader.load (node:internal/modules/esm/loader:603:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:480:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:434:34)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'

The "options" to the fork function was:

{
  "execPath":"",
  "execArgv": [
    "--require",
    "c:\\Users\\redacted\\repo\\.pnp.cjs",
    "--experimental-loader",
    "c:\\Users\\redacted\\repo\\.pnp.loader.mjs"
  ],
  "env": {
    "ELECTRON_RUN_AS_NODE":"1",
    "ELECTRON_USE_V8_CONFIGURED_PARTITION_POOL":true
  },
  "stdio":"overlapped",
  "cwd": "C:/Users/redacted/repo"
}

Back where this comes from should be

vscode/src/api/resolve.ts

Lines 55 to 57 in dad5884

	const pnpPath = require.resolve('./.pnp.cjs', {
	paths: [folder.uri.fsPath],
	})

There, pnpPath is c:\Users\redacted\repo\.pnp.cjs and folder.uri.fsPath is c:\Users\redacted\repo.

Honestly, I am not sure, how this works on non-Windows platforms. I would assume that the path is also absolute but then again it complains that it is not file://?

Thank you in advance!

(Unrelated note: The "Contributing" link for the issue template is broken.)

Reproduction

Any yarn pnp project on windows, I assume.

System Info

System:
    OS: Windows 11 10.0.22621
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-1370P
    Memory: 32.30 GB / 63.66 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.1.1 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.12.1 - C:\Program Files\nodejs\pnpm.CMD
  IDEs:
    VSCode: 1.87.2 - C:\Program Files\Microsoft VS Code\bin\code.CMD
  Browsers:
    Edge: Chromium (122.0.2365.92)
    Internet Explorer: 11.0.22621.1

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• 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.

[sheremet-va]

Yarn PnP is not supported yet.

[sheremet-va]

Also, please provide a minimal Yarn PnP project.

[github-actions]

Hello @Nithanim-Work. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.