[BUG]vitest plugin reports errors in vsocode

[bd-dxg]

Describe the bug

I don't have the vitest dependency package installed, because my current project is not tested, but I'm building the project with vite+, which requires me to install vitest and the vscode plugin for oxc

vp env current

Environment:
  Version      25.8.0
  Source       default
  Source Path  C:\Users\bddxg\.vite-plus\config.json

Tool Paths:
  node  C:\Users\bddxg\.vite-plus\js_runtime\node\25.8.0\node.exe
  npm   C:\Users\bddxg\.vite-plus\js_runtime\node\25.8.0\npm.cmd
  npx   C:\Users\bddxg\.vite-plus\js_runtime\node\25.8.0\npx.cmd

vp --version

vp v0.1.11

Local vite-plus:
  vite-plus  v0.1.11

Tools:
  vite             v8.0.0
  rolldown         v1.0.0-rc.9
  vitest           v4.1.0
  oxfmt            v0.40.0
  oxlint           v1.55.0
  oxlint-tsgolint  v0.16.0
  tsdown           v0.21.2

As shown in the message below, the vitest plugin for vscode is reporting an error.

[INFO 09:36:45] [v1.48.1] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 09:36:45] [API] Resolving configs: medical-system/vite.config.ts
[09:36:45] [API] Spawning on-demand process...
[INFO 09:36:45] [API] Running Vitest v0.1.11 (medical-system/vite.config.ts) with "C:\Users\bddxg\.vite-plus\bin\node.CMD C:/Users/bddxg/.vscode/extensions/vitest.explorer-1.48.1/dist/worker.js"
[Error 09:36:45] There were errors during config load.
[Error 09:36:45] [Error Error] spawn EINVAL
Error: spawn EINVAL
	at ChildProcess.spawn (node:internal/child_process:420:11)
	at spawn (node:child_process:820:9)
	at bt (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:61714)
	at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
	at async Ot (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:69721)
	at async At (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:71681)
	at async er._defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2869)
	at async er.defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2157)
	at async er.activate (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:10786)
	at async Qn (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:748)
	at async zv._activate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15965)
	at async zv._waitForDepsThenActivate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15907)
	at async zv._initialize (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15274)
[Error 09:36:46] [Error Error] The extension could not load any config.
Error: The extension could not load any config.
	at At (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:72070)
	at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
	at async er._defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2869)
	at async er.defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2157)
	at async er.activate (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:10786)
	at async Qn (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:748)
	at async zv._activate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15965)
	at async zv._waitForDepsThenActivate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15907)
	at async zv._initialize (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15274)
[INFO 09:39:00] [DECOR] Decorations for c:\Users\bddxg\.claude\CLAUDE.md are already cached. Displaying them.

Expected behavior

I just opened vscode , I don't want to see these errors

Reproduction

Due to the project, I can't provide a minimal reproduction of the structure, it's just a normal project.

Output

[INFO 09:36:45] [v1.48.1] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 09:36:45] [API] Resolving configs: medical-system/vite.config.ts
[09:36:45] [API] Spawning on-demand process...
[INFO 09:36:45] [API] Running Vitest v0.1.11 (medical-system/vite.config.ts) with "C:\Users\bddxg\.vite-plus\bin\node.CMD C:/Users/bddxg/.vscode/extensions/vitest.explorer-1.48.1/dist/worker.js"
[Error 09:36:45] There were errors during config load.
[Error 09:36:45] [Error Error] spawn EINVAL
Error: spawn EINVAL
	at ChildProcess.spawn (node:internal/child_process:420:11)
	at spawn (node:child_process:820:9)
	at bt (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:61714)
	at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
	at async Ot (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:69721)
	at async At (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:71681)
	at async er._defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2869)
	at async er.defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2157)
	at async er.activate (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:10786)
	at async Qn (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:748)
	at async zv._activate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15965)
	at async zv._waitForDepsThenActivate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15907)
	at async zv._initialize (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15274)
[Error 09:36:46] [Error Error] The extension could not load any config.
Error: The extension could not load any config.
	at At (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:1:72070)
	at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
	at async er._defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2869)
	at async er.defineTestProfiles (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:2157)
	at async er.activate (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:10786)
	at async Qn (c:\Users\bddxg\.vscode\extensions\vitest.explorer-1.48.1\dist\extension.js:12:748)
	at async zv._activate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15965)
	at async zv._waitForDepsThenActivate (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15907)
	at async zv._initialize (file:///c:/Users/bddxg/AppData/Local/Programs/Microsoft%20VS%20Code/ce099c1ed2/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:494:15274)
[INFO 09:39:00] [DECOR] Decorations for c:\Users\bddxg\.claude\CLAUDE.md are already cached. Displaying them.

Extension Version

1.48.1

Vitest Version

4.1.0

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.

[bd-dxg]

I'll add to vite.config.ts

import vue from '@vitejs/plugin-vue'
import { fileURLToPath } from 'node:url'
import { VantResolver } from 'unplugin-vue-components/resolvers'
import Components from 'unplugin-vue-components/vite'
import vueDevTools from 'vite-plugin-vue-devtools'
import { defineConfig } from 'vite-plus'
// https://vite.dev/config/
export default defineConfig({
  fmt: {
    printWidth: 120,
    tabWidth: 2,
    useTabs: false,
    semi: false,
    singleQuote: true,
    quoteProps: 'as-needed',
    bracketSpacing: true,
    arrowParens: 'avoid',
    htmlWhitespaceSensitivity: 'ignore',
    bracketSameLine: true,
    sortPackageJson: true,
    sortImports: {
      groups: [
        ['value-builtin', 'value-external'],
        ['value-internal', 'value-parent', 'value-sibling', 'value-index'],
        {
          newlinesBetween: true,
        },
        'type-import',
        'unknown',
      ],
    },
    ignorePatterns: [],
  },
  lint: {
    plugins: ['vue', 'typescript', 'unicorn', 'oxc', 'import'],
    env: {
      builtin: true,
    },
    ignorePatterns: ['**/dist/**', '**/dist-ssr/**', '**/coverage/**'],
    options: {
      typeAware: true,
      typeCheck: true,
    },
  },
  plugins: [
    vue(),
    vueDevTools(),
    Components({
      dts: fileURLToPath(new URL('src/types/components.d.ts', import.meta.url)),
      resolvers: [VantResolver({ importStyle: false })],
    }),
  ],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('src', import.meta.url)),
    },
  },
})

[sheremet-va]

Your Node path seems wrong, did you update it manually or run any commands to update it? Vitest picks up C:\Users\bddxg\.vite-plus\bin\node.CMD 🤔 but it should be .EXE, not .CMD

[sheremet-va]

Can you run this command and show what's in the PATH?

echo $env:Path

[fengmk2]

The bug has been confirmed to be caused by Vite+'s Node.js runtime shims, which prevents the vitest extension from correctly finding node.exe to execute scripts.
I will attempt to resolve this through the optimization suggestion at voidzero-dev/vite-plus#835

[Anoesj]

@fengmk2 Does that explain the following errors from the Vitest extension (that started after switching to the vp node shims) as well?

Error: Vitest failed to start:
DataCloneError: #<Object> could not be cloned.
    at new DOMException (node:internal/per_context/domexception:76:18)
    at structuredClone (node:internal/worker/js_transferable:126:26)
    at getVitestConfigFromNuxt (file:///<obfuscated>/node_modules/.pnpm/@nuxt+test-utils@4.0.0_@playwright+test@1.58.2_happy-dom@20.8.3_magicast@0.5.2_playwrig_94bbfd3570bae30c338a006062aed329/node_modules/@nuxt/test-utils/dist/config.mjs:131:39)
    at resolveConfig (file:///<obfuscated>/node_modules/.pnpm/@nuxt+test-utils@4.0.0_@playwright+test@1.58.2_happy-dom@20.8.3_magicast@0.5.2_playwrig_94bbfd3570bae30c338a006062aed329/node_modules/@nuxt/test-utils/dist/config.mjs:295:5)
    at file:///<obfuscated>/node_modules/.pnpm/@nuxt+test-utils@4.0.0_@playwright+test@1.58.2_happy-dom@20.8.3_magicast@0.5.2_playwrig_94bbfd3570bae30c338a006062aed329/node_modules/@nuxt/test-utils/dist/config.mjs:233:28
    at resolveTestProjectConfigs (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:10529:68)
    at resolveProjects (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:10326:64)
    at Vitest._setServer (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:12227:20)
    at BasicMinimalPluginContext.handler (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:13158:6)
    at _createServer (file:///<obfuscated>/node_modules/.pnpm/vite@7.3.1_@types+node@25.4.0_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vite/dist/node/chunks/config.js:25603:86)
    at createViteServer (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:9870:17)
    at Module.createVitest (file:///<obfuscated>/node_modules/.pnpm/vitest@4.0.18_@types+node@25.4.0_happy-dom@20.8.3_jiti@2.6.1_sass-embedded@1.98.0_sass@1.98.0_terser@5.46.0_yaml@2.8.2/node_modules/vitest/dist/chunks/cli-api.B7PN_QUv.js:13186:17)
    at Module.ue (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/workerNew.js:3:8989)
    at e.t (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/worker.js:1:1267)
	at e.l (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/extension.js:1:60282)
	at e.emit (node:events:519:28)
	at e.o.t.exports.ae (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:38577)
	at e.o.t.exports.emit (node:events:519:28)
	at e.o.t.exports.dataMessage (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:16501)
	at e.o.t.exports.getData (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:15398)
	at e.o.t.exports.startLoop (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:12110)
	at e.o.t.exports._write (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:11402)
	at writeOrBuffer (node:internal/streams/writable:572:12)
	at _write (node:internal/streams/writable:501:10)
	at Writable.write (node:internal/streams/writable:510:10)
	at Socket.Z (/home/anoesj/.vscode/extensions/vitest.explorer-1.48.1/dist/wrapper-Br94zcvg.js:1:39601)
	at Socket.emit (node:events:519:28)
	at addChunk (node:internal/streams/readable:561:12)
	at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
	at Readable.push (node:internal/streams/readable:392:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
	at TCP.callbackTrampoline (node:internal/async_hooks:130:17)

[fengmk2]

@Anoesj Looking at the error stack, it's not the same issue. The problem I confirmed only exists on Windows.

[sheremet-va]

@fengmk2 Does that explain the following errors from the Vitest extension (that started after switching to the vp node shims) as well?

Do you have an example of your config? According to the stack, it might be a bug in Nuxt where it tries to clone extra properties (since there are now more options in the config, some of them might not be clonable)

[sheremet-va]

Seems like this is resolved in voidzero-dev/vite-plus#981