Recordsnpm@types/nodefailure issue
Failure signature
PROJECT_TEST exit 1 ×4
[31m[1mAssertionError[22m: expected [ { kind: <str>, …(2) } ] to deeply equal [][39m · [32m- Expected[39m · [31m+ Received[39m · [32m- [][39m
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-09 · Last seen: 2026-09-09
sha256:87a2d9024768…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 26.4.1 PASS 11 passing observations
- 26.4.0 PASS 7 passing observations
- 26.3.0 not measured
- 26.2.0 FAIL
- 26.1.2 PASS 1 passing observations
- 24.13.5 PASS 23 passing observations
- 24.13.3 FAIL
- 24.13.2 not measured
- 22.20.3 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×4 2026-09-09 → 2026-09-09
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 22.20.3 → first failing release 24.13.3
Releases between them never measured at this stage: 1
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.
-
Last passing release 26.1.2 → first failing release 26.2.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 26.2.0 → first passing release 26.4.0
Releases between them never measured at this stage: 1
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.4.1 | 26.4.0 | 26.2.0 | 26.1.2 | 24.13.5 | 24.13.3 | 22.20.3 |
|---|---|---|---|---|---|---|---|
| undici-types | 8.3.0 | 8.3.0 | 8.3.0 | 8.3.0 | 7.18.2 | 7.18.2 | 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_TEST: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @types/node 26.2.0 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. HOW MIT-0 · 2026-08-23
- @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