fix(tests): stop esbuild child process in global teardown for Node 22 CI

Node 22 changed stream.pipeline() to wait for the "close" event before
completing (nodejs/node#53462). Vite's internal esbuild child process
holds stdio handles open indefinitely, preventing the event loop from
draining after tests finish. This causes vitest to hang in CI on Node 22
even though all tests pass.

Adding a global teardown that calls esbuild.stop() explicitly kills the
esbuild process and releases its handles so vitest can exit cleanly.

Author: saoudrizwan

test/vitest-global-teardown.ts

@@ -0,0 +1,14 @@
+import { stop as stopEsbuild } from "esbuild";
+
+// Node 22 changed stream.pipeline() to wait for the "close" event before
+// completing (nodejs/node#53462). The esbuild child process that vite spawns
+// for TypeScript transforms holds stdio handles open indefinitely, which
+// prevents the Node event loop from draining after tests finish. Explicitly
+// stopping esbuild releases those handles so vitest can exit cleanly.
+//
+// On Node 20 (and locally on Node 22 with faster shutdown timing), vitest
+// exits before this becomes a problem. In CI on Node 22, the slower runner
+// timing consistently triggers the hang.
+export async function teardown(): Promise<void> {
+	await stopEsbuild();
+}

vitest.config.ts

@@ -18,6 +18,7 @@ export default defineConfig({
 	test: {
 		globals: true,
 		environment: "node",
+		globalSetup: ["./test/vitest-global-teardown.ts"],
 		exclude: ["apps/**", "web-ui/**", "third_party/**", "**/node_modules/**", "**/dist/**", ".worktrees/**"],
 		testTimeout: 15_000,
 	},