The four repo-root `vitest.setup.*` files are in zero tsc programs — #3476 one directory up

[yinlianghui]

Observation-class finding, tripped over while implementing #3476 (PR #3513). Nothing a user hits today — recording it so it does not stay invisible. Not fixed in #3513: the fix lands in a root tsconfig, which was outside that task's file fence.

The gap

Four checked-in files at the repo root are compiled by nothing:

vitest.setup.base.ts
vitest.setup.dom.tsx
vitest.setup.dom-light.tsx
vitest.setup.tsx

Measured on the #3476 branch (same result on origin/main @ f995a45):

$ ./node_modules/.bin/tsc -p tsconfig.json        --listFilesOnly | grep -c 'objectui/vitest.setup.dom.tsx'
0
$ ./node_modules/.bin/tsc -p tsconfig.scripts.json --listFilesOnly | grep -c 'objectui/vitest.setup.dom.tsx'
0

Why nothing reaches them:

• They sit at the repo root, outside every workspace package (pnpm-workspace.yaml: packages/*, examples/*, apps/*, docs), so turbo run type-check — which is driven by package.json scripts — structurally cannot see them. Same reason scripts/ was uncovered until [ci] scripts/ 在零 tsconfig 覆盖内:turbo type-check 从不检查 scripts/__tests__/*.ts——一批门禁 pin 测试自身无类型门 #3494.
• Root tsconfig.json's include is packages / examples / apps; tsconfig.scripts.json's is scripts/**. Neither matches the root directory itself.
• They are never imported by anything under packages / examples / apps either, so no gated program pulls them in transitively. Every consumer names them as a Vitest setupFiles runtime path string (setupFiles: ['../../vitest.setup.tsx'], path.resolve(import.meta.dirname, '../../vitest.setup.dom.tsx'), ...). The one real import edge is internal: vitest.setup.dom.tsx line 15 imports ./vitest.setup.base.

The only program that does contain them is the root tsconfig.node.json (no include, so it defaults to the whole root directory) — and no script anywhere runs that file, so it is not a gate.

Why it is worth recording

This is exactly the #3476 shape one directory up, and the #3494 shape one directory over: a checked-in .ts/.tsx file that reads as ordinary maintained source while no tsc invocation has ever looked at it.

The content is not trivial plumbing either. vitest.setup.dom.tsx decides which of four side-effect package graphs get registered before the dom-heavy project runs, and vitest.setup.base.ts is imported by it. Drift there does not fail loudly with a type error — it fails as a confusing "component not registered" in whichever test happens to depend on the registration.

Impact today: nil. They are small and currently correct; a break would surface as a red test run rather than silently. That is why this is finding and not queued.

Not the same as the per-package setup files

Checked while measuring, so nobody re-checks it: the ./vitest.setup.ts that seven package vitest configs reference (plugin-kanban, plugin-calendar, plugin-detail, plugin-gantt, plugin-charts, plugin-form, plugin-designer) all exist, and they live inside their package, so they are reachable by that package's own tsconfig. No ghost entries there.

Shape of a fix (for whoever picks it up)

Not obvious enough to prescribe — the options differ in blast radius and want measuring, the way #3494 measured allowJs:

1. Add the root vitest.setup.* files to tsconfig.scripts.json's include. Cheap, but that project is named and documented for scripts/, and it sets allowJs: true — which is the option that turned five @ts-expect-error comments stale in ci(scripts): 用独立 tsconfig.scripts.json 给 scripts/ 补上类型门 (#3494) #3498 and is still doing so in main 的 Type Check job 全红:#3489 与 #3498 的语义冲突,check-doc-links.test.ts 的 @ts-expect-error 在 allowJs 下变成 TS2578 #3504. A .tsx also needs jsx and DOM lib, which that project does not set.
2. A small dedicated root project for them, mirroring how [ci] scripts/ 在零 tsconfig 覆盖内:turbo type-check 从不检查 scripts/__tests__/*.ts——一批门禁 pin 测试自身无类型门 #3494 handled scripts/, wired into ci.yml next to type-check:scripts. Most consistent with precedent; costs one more config and one more CI step.
3. Widen the root tsconfig.json and give it a runner. Largest blast radius — that file is currently the editor config and nothing runs it; making it a gate is a separate decision with its own error backlog.

Whichever route, the reverse verification is the same as #3513's: plant a real type error in one of the four files and confirm the chosen gate goes red, having predicted that direction first.

Related: #3476 / PR #3513 (this file family's neighbour), #3494 / PR #3498 (scripts/), #3305 (the console node project), #3504 (the live allowJs / TS2578 interaction option 1 would inherit).

---

Generated by Claude Code

[yinlianghui]

认领(发现分诊轮晋级)— 会话 session_01GTRjn8xBqp75dk7kFupVRt,分支 claude/issue-3515-root-setup-tsc。

分诊裁定:取 issue 的路线 2(为四个根 vitest.setup.* 文件建一个小型专用 root tsconfig 项目,镜像 #3494 处理 scripts/ 的先例,接进 ci.yml 挨着 type-check:scripts)。路线 1 否决(tsconfig.scripts.json 名实为 scripts/、且 allowJs:true 会引爆 TS2578 地雷、还缺 jsx/DOM lib);路线 3 否决(把编辑器配置变门禁是带着错误积压的独立决策)。本仓已为"checked-in 但零 tsc 程序"这一类付过三次学费(#3494/#3476/本单),预防价一次比一次便宜。逆向验证按 issue 写的做:植入真类型错、预告方向、确认新门变红。⚠️ 注意 #3513 刚合并的 turbo inputs 教训:若新项目读到包目录外的文件,turbo(或 ci.yml 直跑)的缓存键要一并核对,别再造一个"缓存态决定判决"的半武装门。

文件面:新 root tsconfig(命名依 #3494 先例)、.github/workflows/ci.yml(仅新增 step)、package.json(仅新增 script)、必要时四个 setup 文件内新暴露的真类型错修复。越界即停。

---

Generated by Claude Code

[yinlianghui]

验收:ACCEPT — PR #3550(收尾批最后一单)。

核过实物(git 三点差恰 5 文件,+487/-1)。裁定要点:

1. 唯一真实设计决策被三路实测取代了猜测:根 node_modules 无链接使普通解析结构性不可能;paths→src 在别包的宽松 strictness 下产出 30 个此处不可修的错(正是 tsconfig.scripts.json 记载的"此绿彼红"陷阱);选定 paths→包目录让 TS 跟随各包自己的 exports.types —— 0 错、4.5s、映射跟着包声明走而非写死 dist/。
2. 选项逐项消融(lib/DOM 14 错、.tsx 解析即需 jsx 哪怕无 JSX、skipLibCheck 的"为什么"落在第三方 .d.ts 上不弱化主体)、allowJs 不设是量出来的并有钉扎防未来误开(ci(console): 把 vitest.config.ts 纳入 tsc program,并把根 vitest 配置算进 turbo 的 cache key #3513 的 TS2578 雷区)。
3. CI 落位的差异是承重的:直接 ci.yml 步(零 turbo 缓存键参与 —— ci(console): 把 vitest.config.ts 纳入 tsc program,并把根 vitest 配置算进 turbo 的 cache key #3513 教训的显式回答),且排在 pnpm type-check 之后(依赖 ^build 闭包产出的声明文件,实测四个包都在闭包内),与 type-check:scripts 的"零工作区依赖"前提相反 —— 两侧都有钉扎。剩余风险(某包失去全部依赖者时 ^build 不再建它)如实声明、失败响亮,不过度加机械。
4. 证据纪律三连:预测落空一次(as Storage 吸收成员错配)如实上报换了明确错型重做;自己钉扎测试里的空转绿被自己抓出(fileNames 只含根集 → 改真 createProgram);变异扫描逐条咬合。
5. 两处围栏偏离均背书:钉扎测试文件(DoD 要求 + ci(scripts): 用独立 tsconfig.scripts.json 给 scripts/ 补上类型门 (#3494) #3498 先例恰好就是此物)与 ci-cd-pipeline.md 第 69 行表格格(ci(scripts): 用独立 tsconfig.scripts.json 给 scripts/ 补上类型门 (#3494) #3498 改过同一格,不改则 prose 枚举缺步)。
6. 过程事故完整披露:tsconfig.node.json 裸跑喷出 5838 个工件、被 wip 提交吞掉、165 个 rolldown 错误误导为"你改坏了构建"—— 干净恢复、全部验证重跑,并把陷阱本身立为 Root tsconfig.node.json emits build artifacts next to every source — 5,838 files, none of them gitignored #3549(按暂停纪律冻结入池)。这个事故报告本身就是 Root tsconfig.node.json emits build artifacts next to every source — 5,838 files, none of them gitignored #3549 的最好证据。

PR 转 ready + auto-merge(配额恢复后执行,undraft 队列第 6 位)。在飞归零 —— 收尾进入最后阶段:6 个 PR 全 MERGED 后车道完全静默。

---

Generated by Claude Code