Recordsnpmqsfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 2 !== 0 · at TestContext.<anonymous> (<url>) …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:0cab186a142b…
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.
- 6.16.0 FAIL
- 6.15.3 PASS 187 passing observations
- 6.14.0 PASS 1 passing observations
- 6.13.0 PASS 2 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-09-13 → 2026-09-13
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 6.15.3 → first failing release 6.16.0
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 | 6.16.0 | 6.15.3 | 6.13.0 |
|---|---|---|---|
| es-define-property | 1.0.1 | 1.0.1 | — |
| side-channel | 1.1.1 | 1.1.1 | 1.1.1 |
Moved: 0 · unchanged at every release: 2
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
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.