CodeSampleX

Recordsnpm@types/nodefailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×2

...pData\Local\Temp\capturepack-share-check-runner-nYgkN2\check.cjs 203.6kb · Done in 12ms …

Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-01 · Last seen: 2026-09-01

sha256:50b8bb0ef446…

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

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.

Library26.1.224.13.524.13.322.20.322.19.122.10.220.19.4317.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

Published answers for the affected releases

Back to the package