chore(v2): vitest 4 (#8084)

Author: wmertens

.changeset/free-needles-live.md

@@ -0,0 +1,5 @@
+---
+'@qwik.dev/core': patch
+---
+
+FEAT: All vite.config.mts files got renamed to vite.config.ts files, because all starters are marked as ESM projects

.vscode/launch.json

@@ -38,7 +38,7 @@
       "skipFiles": ["<node_internals>/**"],
       "cwd": "${workspaceFolder}/packages/docs",
       "program": "${workspaceFolder}/packages/docs/node_modules/vite/bin/vite.js",
-      "args": ["build", "-c", "adapters/cloudflare-pages/vite.config.mts"]
+      "args": ["build", "-c", "adapters/cloudflare-pages/vite.config.ts"]
     },
     {
       "type": "node",

e2e/qwik-cli-e2e/README.md

@@ -47,4 +47,4 @@ Both `config.cleanupFn();` and `killAllRegisteredProcesses` there are extremely
 
 ## Adding new tests
 
-Right now we have only one test file within this project. This means only one test application will be created and used, which is good from the execution time standpoint. If more files are added, it shouldn't potentially be a problem as we have `fileParallelism: false` set in the `vite.config.mts`, which means only one test will be executed at a time. This obviously slows down the execution time, but is safer, because we're working with a real file system.
+Right now we have only one test file within this project. This means only one test application will be created and used, which is good from the execution time standpoint. If more files are added, it shouldn't potentially be a problem as we have `fileParallelism: false` set in the `vite.config.ts`, which means only one test will be executed at a time. This obviously slows down the execution time, but is safer, because we're working with a real file system.

e2e/qwik-cli-e2e/package.json

@@ -6,7 +6,7 @@
   },
   "private": true,
   "scripts": {
-    "e2e": "vitest run --config=vite.config.mts",
-    "e2e.watch": "vitest watch --config=vite.config.mts"
+    "e2e": "vitest run --config=vite.config.ts",
+    "e2e.watch": "vitest watch --config=vite.config.ts"
   }
 }

e2e/qwik-cli-e2e/vite.config.mts renamed to e2e/qwik-cli-e2e/vite.config.ts

@@ -161,7 +161,7 @@
     "vite-imagetools": "9.0.0",
     "vite-plugin-dts": "4.5.4",
     "vite-tsconfig-paths": "5.1.4",
-    "vitest": "3.2.4",
+    "vitest": "4.0.1",
     "watchlist": "0.3.1",
     "which-pm-runs": "1.1.0",
     "zod": "3.25.48"

package.json

@@ -26,9 +26,9 @@
         }
       ],
       "kind": "Interface",
-      "content": "```typescript\nexport interface VercelEdgeAdapterOptions extends ServerAdapterOptions \n```\n**Extends:** ServerAdapterOptions\n\n\n<table><thead><tr><th>\n\nProperty\n\n\n</th><th>\n\nModifiers\n\n\n</th><th>\n\nType\n\n\n</th><th>\n\nDescription\n\n\n</th></tr></thead>\n<tbody><tr><td>\n\n[outputConfig?](./router.verceledgeadapteroptions.outputconfig.md)\n\n\n</td><td>\n\n\n</td><td>\n\nboolean\n\n\n</td><td>\n\n_(Optional)_ Determines if the build should auto-generate the `.vercel/output/config.json` config.\n\nDefaults to `true`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[staticPaths?](./router.verceledgeadapteroptions.staticpaths.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\\[\\]\n\n\n</td><td>\n\n_(Optional)_ Manually add pathnames that should be treated as static paths and not SSR. For example, when these pathnames are requested, their response should come from a static file, rather than a server-side rendered response.\n\n\n</td></tr>\n<tr><td>\n\n[target?](./router.verceledgeadapteroptions.target.md)\n\n\n</td><td>\n\n\n</td><td>\n\n'webworker' \\| 'node'\n\n\n</td><td>\n\n_(Optional)_ Define the `target` property in the `ssr` object in the `vite.config.mts` file.\n\nDefaults to `webworker`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[vcConfigEntryPoint?](./router.verceledgeadapteroptions.vcconfigentrypoint.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\n\n\n</td><td>\n\n_(Optional)_ The `entrypoint` property in the `.vc-config.json` file. Indicates the initial file where code will be executed for the Edge Function.\n\nDefaults to `entry.vercel-edge.js`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[vcConfigEnvVarsInUse?](./router.verceledgeadapteroptions.vcconfigenvvarsinuse.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\\[\\]\n\n\n</td><td>\n\n_(Optional)_ The `envVarsInUse` property in the `.vc-config.json` file. List of environment variable names that will be available for the Edge Function to utilize.\n\nDefaults to `undefined`<!-- -->.\n\n\n</td></tr>\n</tbody></table>",
+      "content": "```typescript\nexport interface VercelEdgeAdapterOptions extends ServerAdapterOptions \n```\n**Extends:** ServerAdapterOptions\n\n\n<table><thead><tr><th>\n\nProperty\n\n\n</th><th>\n\nModifiers\n\n\n</th><th>\n\nType\n\n\n</th><th>\n\nDescription\n\n\n</th></tr></thead>\n<tbody><tr><td>\n\n[outputConfig?](./router.verceledgeadapteroptions.outputconfig.md)\n\n\n</td><td>\n\n\n</td><td>\n\nboolean\n\n\n</td><td>\n\n_(Optional)_ Determines if the build should auto-generate the `.vercel/output/config.json` config.\n\nDefaults to `true`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[staticPaths?](./router.verceledgeadapteroptions.staticpaths.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\\[\\]\n\n\n</td><td>\n\n_(Optional)_ Manually add pathnames that should be treated as static paths and not SSR. For example, when these pathnames are requested, their response should come from a static file, rather than a server-side rendered response.\n\n\n</td></tr>\n<tr><td>\n\n[target?](./router.verceledgeadapteroptions.target.md)\n\n\n</td><td>\n\n\n</td><td>\n\n'webworker' \\| 'node'\n\n\n</td><td>\n\n_(Optional)_ Define the `target` property in the `ssr` object in the `vite.config.ts` file.\n\nDefaults to `webworker`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[vcConfigEntryPoint?](./router.verceledgeadapteroptions.vcconfigentrypoint.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\n\n\n</td><td>\n\n_(Optional)_ The `entrypoint` property in the `.vc-config.json` file. Indicates the initial file where code will be executed for the Edge Function.\n\nDefaults to `entry.vercel-edge.js`<!-- -->.\n\n\n</td></tr>\n<tr><td>\n\n[vcConfigEnvVarsInUse?](./router.verceledgeadapteroptions.vcconfigenvvarsinuse.md)\n\n\n</td><td>\n\n\n</td><td>\n\nstring\\[\\]\n\n\n</td><td>\n\n_(Optional)_ The `envVarsInUse` property in the `.vc-config.json` file. List of environment variable names that will be available for the Edge Function to utilize.\n\nDefaults to `undefined`<!-- -->.\n\n\n</td></tr>\n</tbody></table>",
       "editUrl": "https://github.com/QwikDev/qwik/tree/main/packages/qwik-router/src/adapters/vercel-edge/vite/index.ts",
       "mdFile": "router.verceledgeadapteroptions.md"
     }
   ]
-}
+}

packages/docs/src/routes/api/qwik-router-vite-vercel/api.json

@@ -113,7 +113,7 @@ _(Optional)_ Manually add pathnames that should be treated as static paths and n
 
 </td><td>
 
-_(Optional)_ Define the `target` property in the `ssr` object in the `vite.config.mts` file.
+_(Optional)_ Define the `target` property in the `ssr` object in the `vite.config.ts` file.
 
 Defaults to `webworker`.
 

packages/docs/src/routes/api/qwik-router-vite-vercel/index.mdx

@@ -21,7 +21,7 @@ In certain cases, we may need to make the build output directory different from
 
 Usually with Vite.js we do it like this:
 
-```ts title="vite.config.mts"
+```ts title="vite.config.ts"
 import { defineConfig } from 'vite';
 import { qwikVite } from '@qwik.dev/core/optimizer';
 import { qwikRouter } from '@qwik.dev/router/vite';
@@ -56,7 +56,7 @@ However, it will be overridden by the settings of QwikVite() so nothing happens
 
 So instead of changing the settings in Vite.js directly, we just need to change the settings in QwikVite() like this:
 
-```ts title="vite.config.mts"
+```ts title="vite.config.ts"
 import { defineConfig } from 'vite';
 import { qwikVite } from '@qwik.dev/core/optimizer';
 import { qwikRouter } from '@qwik.dev/router/vite';

packages/docs/src/routes/docs/(qwik)/advanced/custom-build-dir/index.mdx

@@ -56,10 +56,10 @@ This will create a new folder called `my-library` with the following structure:
 │   ├── index.ts
 │   └── root.tsx
 ├── tsconfig.json
-└── vite.config.mts
+└── vite.config.ts
 ```
 
-The most important files of a library are a properly configured `package.json` and `vite.config.mts`.
+The most important files of a library are a properly configured `package.json` and `vite.config.ts`.
 
 ## package.json
 
@@ -90,7 +90,7 @@ Notice the `qwik` field, this is the entry point for the Qwik Optimizer, it will
 
 > The file must be called with the `.qwik.mjs` extension, otherwise the Qwik Optimizer will not recognize it.
 
-## vite.config.mts
+## vite.config.ts
 
 ```ts {8-12}
 import { defineConfig } from 'vite';