chore: remove vite-node from the monorepo (#8761)

Author: sheremet-va

AGENTS.md

@@ -44,7 +44,6 @@ Vitest is a next-generation testing framework powered by Vite. This is a monorep
 
 ### Core Packages (`packages/`)
 - `vitest` - Main testing framework
-- `vite-node` - Vite SSR runtime
 - `browser` - Browser testing support
 - `ui` - Web UI for test results
 - `runner` - Test runner core

docs/config/index.md

@@ -156,7 +156,7 @@ Color used by CLI and UI can be changed by providing an object with `color` prop
 
 - **Type:** `{ sourcemap?, deps?, ... }`
 
-Vite-Node server options.
+Moudle runner options.
 
 #### server.sourcemap
 
@@ -169,7 +169,7 @@ Inject inline source map to modules.
 
 - **Type:** `{ dumpModules?, loadDumppedModules? }`
 
-Vite-Node debugger options.
+Module runner debugger options.
 
 #### server.debug.dumpModules
 

docs/guide/profiling-test-performance.md

@@ -79,24 +79,6 @@ After the tests have run there should be a `main-profile/*.cpuprofile` file gene
 
 ## File transform
 
-In cases where your test transform and collection time is high, you can use `DEBUG=vite-node:*` environment variable to see which files are being transformed and executed by `vite-node`.
-
-```bash
-$ DEBUG=vite-node:* vitest --run
-
- RUN  v2.1.1 /x/vitest/examples/profiling
-
-  vite-node:server:request /x/vitest/examples/profiling/global-setup.ts +0ms
-  vite-node:client:execute /x/vitest/examples/profiling/global-setup.ts +0ms
-  vite-node:server:request /x/vitest/examples/profiling/test/prime-number.test.ts +45ms
-  vite-node:client:execute /x/vitest/examples/profiling/test/prime-number.test.ts +26ms
-  vite-node:server:request /src/prime-number.ts +9ms
-  vite-node:client:execute /x/vitest/examples/profiling/src/prime-number.ts +9ms
-  vite-node:server:request /src/unnecessary-file.ts +6ms
-  vite-node:client:execute /x/vitest/examples/profiling/src/unnecessary-file.ts +4ms
-...
-```
-
 This profiling strategy is a good way to identify unnecessary transforms caused by [barrel files](https://vitejs.dev/guide/performance.html#avoid-barrel-files).
 If these logs contain files that should not be loaded when your test is run, you might have barrel files that are importing files unnecessarily.
 
@@ -131,17 +113,15 @@ test('formatter works', () => {
 
 <img src="/module-graph-barrel-file.png" alt="Vitest UI demonstrating barrel file issues" />
 
-To see how files are transformed, you can use `VITE_NODE_DEBUG_DUMP` environment variable to write transformed files in the file system:
+To see how files are transformed, you can use `VITEST_DEBUG_DUMP` environment variable to write transformed files in the file system:
 
 ```bash
-$ VITE_NODE_DEBUG_DUMP=true vitest --run
-
-[vite-node] [debug] dump modules to /x/examples/profiling/.vite-node/dump
+$ VITEST_DEBUG_DUMP=true vitest --run
 
  RUN  v2.1.1 /x/vitest/examples/profiling
 ...
 
-$ ls .vite-node/dump/
+$ ls .vitest-dump/
 _x_examples_profiling_global-setup_ts-1292904907.js
 _x_examples_profiling_test_prime-number_test_ts-1413378098.js
 _src_prime-number_ts-525172412.js

eslint.config.js

@@ -135,11 +135,4 @@ export default antfu(
       'unicorn/consistent-function-scoping': 'off',
     },
   },
-  {
-    files: [`packages/vite-node/${GLOB_SRC}`],
-    rules: {
-      // false positive on "exports" variable
-      'antfu/no-cjs-exports': 'off',
-    },
-  },
 )

packages/utils/src/source-map.ts

@@ -20,8 +20,6 @@ const stackIgnorePatterns: (string | RegExp)[] = [
   /\/@vitest\/\w+\/dist\//,
   '/vitest/dist/',
   '/vitest/src/',
-  '/vite-node/dist/',
-  '/vite-node/src/',
   '/node_modules/chai/',
   '/node_modules/tinyspy/',
   '/vite/dist/node/module-runner',