The file was doubly dead: the vitest include lacked lib/*.test.mjs and the file imported node:test, so no runner ever executed it. The include now picks up lib .mjs tests and the imports move to vitest (node:assert keeps the original assertion style) — all 5 assertions live. (S5) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
22 lines
897 B
TypeScript
22 lines
897 B
TypeScript
import { defineConfig } from "vitest/config";
|
|
|
|
export default defineConfig({
|
|
test: {
|
|
globals: true,
|
|
environment: "node",
|
|
include: ["*.test.ts", "lib/*.test.{ts,mjs}", "__tests__/*.test.ts"],
|
|
clearMocks: true,
|
|
restoreMocks: true,
|
|
// The core-package `*.e2e.test.ts` files each do a full `pnpm install`
|
|
// in a temp clone. Running them in parallel saturates the machine and
|
|
// trips vitest's worker RPC timeout ("Timeout calling onTaskUpdate").
|
|
// Run test files one at a time so each e2e test gets the box to itself.
|
|
fileParallelism: false,
|
|
// Each e2e test's `onTestFinished` cleanup `rmSync`-es a temp clone that
|
|
// contains a full installed `node_modules`. Deleting that many files can
|
|
// exceed vitest's 10s default hook timeout under load, so raise the
|
|
// ceiling to match the 120s per-test timeout.
|
|
hookTimeout: 120_000,
|
|
},
|
|
});
|