Recordsnpm@types/nodefailure issue
Failure signature
UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2
Image hunterzo-egress-lab:local Building · Image hunterzo-egress-lab:local Built · Network hunterzo-egress-lab_fixture_net Creating …
Evidence quality: complete · unclassified-diagnostic · gap stage-unknown · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:340c5f78ca35…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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=esm · os=windows · runtime=node@24.13 ×2 2026-09-14 → 2026-09-14
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.5.1 | 26.4.1 | 26.4.0 |
|---|---|---|---|
| undici-types | 8.9.0 | 8.3.0 | 8.3.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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.