Files
deepseek-harness/vitest.config.ts
Tianyi Cui 583704ac1d feat: add the worker-thread code runtime (dsh-code-runtime-worker)
The shipped backend of the code-execution seam, per the Code Mode RFC's
worker-thread section: one fresh Node worker per run, executing the
model's TypeScript after a host-side type-strip (wrapped in an
async-function shell so top-level return/await parse, sliced back out
position-preserved), bindings bridged over the message port under
hostile-peer rules (own-property name lookup, at-most-once replies,
post-settlement drops, null-prototype namespaces), logs streamed eagerly
with an in-band truncation marker, and two independent budgets — measured
event-loop busy time (computeMs) plus a never-pausing wall ceiling
(maxWallMs) — funneling into worker.terminate(). env: {} and execArgv: []
keep the isolate hermetic; disposal aborts in-flight runs and awaits
worker exits.

The worker entry loads unbuilt via Node's native type stripping
(src/worker.ts, erasable-only) and ships built as a sibling tsdown bundle
(lib/worker.js); tests/built-lib.e2e.ts pins the built load path under
plain node and joins the built-artifact smoke gate. Unit suites cover the
bootstrap in-process (fake port) and the runtime over real workers,
per-file 100%.
2026-07-08 11:07:14 +08:00

55 lines
2.9 KiB
TypeScript

import tsconfigPaths from 'vite-tsconfig-paths'
import { defineConfig } from 'vitest/config'
export default defineConfig({
// Vite ≥8 warns that this plugin can be replaced by the native (experimental)
// `resolve.tsconfigPaths: true`. It cannot — keep the plugin. Tests run
// unbuilt (see AGENTS.md): bare workspace names like `cordis` or
// `@deepseek-ai/dsh-llm` must resolve to src/, and that mapping comes from
// the root tsconfig.json paths map. The native option is a bare boolean:
// for each
// importing file it discovers the NEAREST tsconfig.json and applies that
// file's own `paths`. Every workspace under packages/* and vendor/* has its
// own tsconfig.json without `paths`, so native resolution maps nothing,
// falls through to package.json exports (lib/, absent until `pnpm run build`),
// and every test file fails to import (verified on vite 8.0.16 /
// vitest 4.1.8). Making it work would mean copying the paths map into all
// 15 workspace tsconfigs — including vendor/* ones, which are pinned
// upstream copies (vendor/README.md). The plugin's `projects` option
// instead applies the one root map to every importer.
plugins: [tsconfigPaths({ projects: ['./tsconfig.json'] })],
test: {
include: ['packages/*/*/tests/**/*.spec.ts', 'examples/*/tests/**/*.spec.ts'],
coverage: {
provider: 'v8',
// Coverage measures OUR runtime source. Types-only files carry no
// executable code; vendor/ and examples/ are out of scope (examples are
// exercised by the demo smoke test instead).
include: ['packages/*/*/src/**/*.ts'],
// Types-only files carry no executable code. `bin.ts` files are
// self-executing CLI entrypoints (a top-level `await main()`): a spec
// can't import one without booting it, so they are driven by the keyless
// Loader-path smoke (a real subprocess) instead of the in-process unit
// suite — the same reason `examples/start.ts` sat out of coverage scope.
// `worker.ts` files are the same class as bin.ts: self-executing
// worker-thread entrypoints that only ever run inside a spawned isolate
// the v8 provider cannot observe. They stay thin glue over in-process-
// tested logic (bootstrap.ts) and are pinned by real-worker integration
// tests.
exclude: ['packages/*/*/src/types.ts', 'packages/*/*/src/bin.ts', 'packages/*/*/src/worker.ts'],
// 100% or it doesn't merge (docs/testing.md: excessive tests are welcome).
// Per-file so a well-covered big file can't subsidize a bare one.
// Every v8 ignore comment must carry a reason — see the quality-gates RFC
// (docs/rfc/implemented/process/2026-06-11-quality-gates.md).
thresholds: {
perFile: true,
statements: 100,
branches: 100,
functions: 100,
lines: 100,
},
reporter: process.env.CI ? ['text'] : ['text', 'html'],
},
},
})