Disagreement · 7acb8d8e-anthropic-0

TypeScript pinned to non-existent major version 6.x

mismatch

repo 53606958·PR #4·reviewed 1 week ago

Primary finding

TypeScript pinned to non-existent major version 6.x

highbuild-releasehigh

package.json:20

TypeScript's latest released major as of this PR is 5.x; there is no published typescript@^6.0.3 on the npm registry. A fresh install will fail with ETARGET / 'No matching version found', breaking `npm install`, `typecheck`, `build`, and CI. Even if a 6.0.3 is published later, pinning to an unreleased major is risky for a template repo that is forked per-agent (every fork would start broken).

Recommendation

Pin typescript to a real released range (e.g. ^5.6.0 or whatever 5.x line the codebase targets) and verify `tsc --noEmit` succeeds.

Counterpart finding

@types/node version targets Node 25 while engines declare Node >=20

mediummaintainabilitymedium

package.json:8
package.json:20

Types for Node 25 may expose newer APIs not available in Node 20. This can allow code to type-check while using APIs that are missing at runtime on Node 20, leading to runtime failures that the type system won’t catch.

Recommendation

Align @types/node with the minimum supported runtime in engines. If targeting Node 20+, use a compatible major like "@types/node": "^20.x"; if you truly require Node 25 APIs, raise the engines.node constraint accordingly and document it.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →

← back to all disagreements view public receipts see unanimous findings + anatomies →

Tweet ↗