• Run, debug, and watch Vitest tests in Visual Studio Code.
• NX support (see the NX sample).
• An @open tag can be used when filtering tests, to only show the tests open in the editor.

• Visual Studio Code version >= 1.77.0.
• Vitest version >= v1.4.0

You can identify if your config is loaded by the extension with process.env.VITEST_VSCODE and change the configuration accordingly.

• vitest.rootConfig: The path to your root config file. If you have several Vitest configs, consider using a Vitest workspace.
• vitest.workspaceConfig: The path to the Vitest workspace config file. You can only have a single workspace config per VSCode workspace.
• vitest.configSearchPatternExclude: Glob pattern that should be ignored when this extension looks for config files. Note that this is applied to config files, not test files inside configs. Default: **/{node_modules,.*}/**
• vitest.packagePath: The path to a package.json file of a Vitest executable (it's usually inside node_modules) in case the extension cannot find it. It will be used to resolve Vitest API paths. This should be used as a last resort fix. If the extension cannot find Vitest, please open an issue.
• vitest.nodeExecutable: This extension spawns another process and will use this value as execPath argument.
• vitest.nodeEnv: Environment passed to the runner process in addition to process.env
• vitest.debugExclude: Excludes files matching specified glob patterns from debugging. Default: [\"<node_internals>/**\", \"**/node_modules/**\"]

See https://vitest.dev/guide/workspace.html for monorepo support.

The extension looks for Vitest config or Vitest workspace config to establish the connection with Vitest. If you have several config files, it's recommended to combine them in a single Vitest workspace for a better CPU performance (only have a single Vitest instance instead of several).