fix: don't exclude node_modules by default, only the vitest module

Author: sheremet-va

README.md

@@ -94,7 +94,7 @@ These options are resolved relative to the [workspace file](https://code.visuals
 - `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/**\"]`
+  `["<node_internals>/**"]`
 - `vitest.debugOutFiles`: If source maps are enabled, these glob patterns specify the generated JavaScript files. If a pattern starts with `!` the files are excluded. If not specified, the generated code is expected in the same directory as its source. Default: `["${workspaceFolder}/**/*.(m|c|)js", "!**/node_modules/**"]`
 - `vitest.maximumConfigs`: The maximum amount of configs that Vitest extension can load. If exceeded, the extension will show a warning suggesting to use a workspace config file. Default: `5`
 - `vitest.logLevel`: How verbose should the logger be in the "Output" channel. Default: `info`

packages/extension/src/debug.ts

@@ -50,7 +50,8 @@ export async function debugTests(
 
   const skipFiles = [
     ...(config.debugExclude || []),
-    '**/@vitest/{runner,utils}/*',
+    '**/node_modules/@vitest/{runner,utils}/**',
+    '**/node_modules/vitest/dist/**',
   ]
 
   const debugConfig = {