Recordsnpm@types/nodefailure issue
Failure signature
PROJECT_COMPILE exit 2 TS2741 ×4
src/main/historyWindow.ts(<n>,<n>): error TS2741: Property <str> is missing in type <str> but required in type <str>.
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm run · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:e79354dba35f…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 26.1.2 not measured
- 24.13.5 PASS 19 passing observations
- 24.13.3 FAIL
- 24.13.2 not measured
- 22.20.3 not measured
- 22.20.1 PASS 135 passing observations
- 22.10.2 not measured
- 20.19.43 FAIL
- 17.0.45 PASS 8 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×4 2026-09-01 → 2026-09-01
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 17.0.45 → first failing release 20.19.43
What differs across the boundary
- undici-types — → 6.21.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 20.19.43 → first passing release 22.20.1
Releases between them never measured at this stage: 3
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 22.20.1 → first failing release 24.13.3
Releases between them never measured at this stage: 3
What differs across the boundary
- undici-types 6.21.0 → 7.18.2 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 24.13.3 → first passing release 24.13.5
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 26.1.2 | 24.13.5 | 24.13.3 | 22.20.3 | 22.20.1 | 22.10.2 | 20.19.43 | 17.0.45 |
|---|---|---|---|---|---|---|---|---|
| undici-types | 8.3.0 | 7.18.2 | 7.18.2 | 6.21.0 | 6.21.0 | 6.20.0 | 6.21.0 | — |
Moved: 1 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @types/node 24.13.3 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-21
- @types/node 20.19.43 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-21