Recordsnpmtldtsfailure issue
Failure signature
PROJECT_TEST exit 1 EOF ×1
[31m[1mAssertionError[22m: expected [ <str>, <str>, <str>, <str> ] to deeply equal [ <str>, <str>, <str>, <str> ][39m · [32m- Expected[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:d757efcbaf88…
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.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
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 failing release 6.1.86 → first passing release 7.0.19
What differs across the boundary
- tldts-core 7.0.19 → 6.1.86 evidence
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.
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 | 7.4.11 | 7.0.19 | 6.1.86 |
|---|---|---|---|
| tldts-core | 7.4.11 | 7.0.19 | 6.1.86 |
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
No published sample names these releases.