Type-check coverage gap: e2e/ is outside every tsconfig, so 30 Playwright specs are compiled by nothing #4471

Found while landing #4456 (PR #4470), which closed the lint half of this gap for e2e/. The type-check half is still open, and it is the same defect one gate over.

Measurement

At b4d3c2204, no tsconfig in the repo reaches e2e/:

$ grep -l '"e2e' tsconfig*.json apps/*/tsconfig*.json packages/*/tsconfig*.json
(no matches)

tsconfig.json                 include: ["packages", "examples", "apps"]
tsconfig.scripts.json         include: ["scripts/**/*.ts"]
tsconfig.vitest-setup.json    include: ["./vitest.setup*.ts", "./vitest.setup*.tsx"]
tsconfig.node.json            (no include/files)

e2e/ is not a workspace package, so turbo run type-check structurally cannot reach it either — the same reason given verbatim in tsconfig.scripts.json's header. Playwright transpiles specs without type-checking them, so the 30 .ts files under e2e/ (including e2e/live/global-setup.ts, which runs before every live-suite run) have never been compiled by anything.

Why this is the #3494 shape

#3494 found exactly this for scripts/: "not a workspace package, so turbo run type-check never reaches it, and scripts/__tests__ is matched by no include in the repo". Its resolution is the ready-made remedy shape here:

• a dedicated tsconfig.scripts.json with include: ["scripts/**/*.ts"] — a glob, not a file list, so a new file cannot land outside every program again;
• a named root script type-check:scripts so it is runnable locally, not CI-only;
• a step in ci.yml's type-check job;
• a pin test (scripts/__tests__/scripts-type-check.test.ts) holding the config's parse and glob reach in place.

An e2e twin of that would be a near-mechanical port. Also worth folding in: check-type-check-coverage.mjs has no notion of e2e/ (it derives from workspace packages), so nothing reports this gap the way check-lint-coverage.mjs reports an unlinted package.

One concrete trap for whoever takes it, already measured

The new { cause: e } in e2e/live/global-setup.ts (added by PR #4470 for preserve-caught-error) needs lib: ES2022 or newer — ErrorOptions does not exist in ES2020, and the root tsconfig.json is on target/lib: ES2020:

$ tsc --lib ES2020,DOM ... e2e/live/global-setup.ts
e2e/live/global-setup.ts(28,7): error TS2554: Expected 0-1 arguments, but got 2.

$ tsc --lib ES2022,DOM ... e2e/live/global-setup.ts
(no such error)

So an e2e tsconfig must not simply inherit the root's ES2020 lib. tsconfig.scripts.json already settled the same question the right way for the same reason — "Node 22 (engines.node: ">=22") is what actually runs these files" — and pins target/lib: ES2022. Expect a handful of other standing errors to surface on first compile; that surfacing is the point.

Filed unassigned as a finding while working #4456; not fixed there because it is outside that card's surface (lint wiring plus the 3 error sites).

Generated by Claude Code