Files
openclaw/scripts/run-vitest.d.mts
Peter Steinberger fe261b0f59 chore(tooling): typecheck root test/** with a dedicated tsgo lane (#104475)
* chore(types): add declaration files for scripts/lib and scripts/e2e modules

* chore(types): add declaration files for top-level script modules (a-m)

* chore(types): add declaration files for top-level script modules (n-z)

* test: use a non-secret-shaped gateway token fixture

* test: type ci workflow guard helpers for the root test lane

* chore(tooling): typecheck root test/** with a dedicated tsgo lane

- test/tsconfig/tsconfig.test.root.json: root-test program (strict unused checks,
  fixtures excluded; two Docker E2E clients that import built dist/** stay out,
  same rationale as the scripts/e2e exclusion in tsconfig.scripts.json)
- tsgo:test:root wired into tsgo:test, check:test-types, scripts/check.mjs, and
  the ci.yml test-types shard, mirroring the tsgo:scripts lane (#104348)
- changed-lane routing: test/**/*.ts (excluding fixtures) and the lane tsconfig
  now trigger 'typecheck test root' in check:changed; previously test/ paths ran
  lint only, so harness type errors surfaced first in CI (#104287 envDir case)
- burn down all 1071 latent type errors in the program: precise param/local
  types across test/scripts, test/vitest, test/e2e, and transitive scripts/e2e
  program members; 205 sibling .d.mts declaration files for imported .mjs
  modules (committed separately); zero any, zero ts-expect-error
- resolve the pre-existing testing star-export ambiguity in
  scripts/e2e/parallels/common.ts with an explicit re-export

Closes #104388

* chore(types): correct declaration fidelity per structured review

- re-derive 51 .d.mts files from implementation data flow instead of
  initializers: fix a wrong never return (runTestProjectsDelegation returns
  the child), add encoding-sensitive exec/spawn overloads (plain-gh), restore
  the full release profile union, make parsed paths string | null, add missing
  parseArgs fields via help/non-help unions, add a missing sibling declaration
  (budget-number-args), drop 15 unused lint directives
- precise install-record/tuple typing removes the type-aware oxlint
  regressions the first declarations caused in scripts/e2e implementations
- route .mts declaration edits under test/ to the testRoot lane and reference
  the test-root project from tsconfig.projects.json so tsgo:all covers it
  (closes both review findings against the lane wiring)

* chore(scripts): keep telegram runner dist typing structural for the boundary guard

* chore(types): declare runtime pack and gateway readiness exports added on main

* test: pin the importTargetPlan form of the plugin-contract plan import

The guard expectation still referenced the raw await import( form that
7ae5996bb3 (#103975) replaced with the importTargetPlan fallback helper;
the assertion fails on current main.
2026-07-11 06:15:41 -07:00

77 lines
3.2 KiB
TypeScript

import type { ChildProcess, SpawnOptions } from "node:child_process";
type VitestFs = {
existsSync(path: string): boolean;
symlinkSync?(target: string, path: string, type: string): void;
};
export const DEFAULT_VITEST_NO_OUTPUT_TIMEOUT_MS: 120000;
export const DEFAULT_VITEST_NO_OUTPUT_HEARTBEAT_MS: 30000;
export const DEFAULT_LONG_RUNNING_VITEST_NO_OUTPUT_TIMEOUT_MS: 300000;
export const DEFAULT_EXTRA_LONG_RUNNING_VITEST_NO_OUTPUT_TIMEOUT_MS: 2400000;
export const VITEST_CONFIG_NO_OUTPUT_TIMEOUT_MS: Map<string, number>;
export const TOOLING_EXCLUDED_TESTS: Set<string>;
export function resolveVitestNodeArgs(env?: NodeJS.ProcessEnv): string[];
export function resolveMissingVitestDependencyMessage(baseDir?: string, fsImpl?: VitestFs): string;
export function resolveVitestCliEntry(params?: {
baseDir?: string;
env?: NodeJS.ProcessEnv;
fsImpl?: VitestFs;
platform?: NodeJS.Platform;
requireResolve?: (specifier: string, options?: { paths?: string[] }) => string;
}): string;
export function resolveVitestNoOutputTimeoutMs(env?: NodeJS.ProcessEnv): number | null;
export function resolveVitestNoOutputHeartbeatMs(env?: NodeJS.ProcessEnv): number | null;
export function resolveRunVitestSpawnEnv(
env?: NodeJS.ProcessEnv,
argv?: string[],
): NodeJS.ProcessEnv;
export function resolveDefaultVitestNoOutputTimeoutMs(argv?: string[]): number;
export function resolveVitestSpawnParams(
env?: NodeJS.ProcessEnv,
platform?: NodeJS.Platform,
): SpawnOptions & { env: NodeJS.ProcessEnv; detached: boolean; stdio: string[] };
export function shouldSuppressVitestStderrLine(line: string): boolean;
export function resolveDirectNodeVitestArgs(pnpmArgs: string[]): string[] | null;
export function resolveExplicitTestFileNoPassArgs(argv: string[]): string[];
export function resolveTestProjectsDelegationArgs(argv: string[], cwd?: string): string[] | null;
export function resolveMissingExplicitTestFiles(
argv: string[],
cwd?: string,
fsImpl?: VitestFs,
): string[];
export function resolveImplicitVitestArgs(argv: string[], cwd?: string): string[];
export function installVitestNoOutputWatchdog(params: {
streams?: Array<{ on(event: string, listener: (...args: unknown[]) => void): unknown } | null>;
timeoutMs: number | null;
heartbeatMs?: number | null;
label?: string;
forceKillAfterMs?: number;
log?: (message: string) => void;
onTimeout?: () => void;
onForceKill?: () => void;
setTimeoutFn?: typeof setTimeout;
clearTimeoutFn?: typeof clearTimeout;
}): () => void;
export function spawnWatchedVitestProcess(params: {
pnpmArgs: string[];
spawnParams: SpawnOptions;
env: NodeJS.ProcessEnv;
label?: string;
onNoOutputTimeout?: () => void;
}): {
child: ChildProcess;
getForwardedSignal: () => NodeJS.Signals | null;
teardown: () => void;
};
export function resolveTestProjectsRunnerEnv(env: NodeJS.ProcessEnv): NodeJS.ProcessEnv;
export function resolveTestProjectsRunnerSpawnParams(
env: NodeJS.ProcessEnv,
platform?: NodeJS.Platform,
): SpawnOptions & { env: NodeJS.ProcessEnv; detached: boolean; stdio: "inherit" };
export function runTestProjectsDelegation(
argv: string[],
env: NodeJS.ProcessEnv,
options?: { runnerPath?: string },
): ChildProcess;