Recordsnpmaggregate-errorfailure 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-14 · Last seen: 2026-09-14
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-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 | 5.0.0 | 3.1.0 |
|---|---|---|
| clean-stack | 5.3.0 | 2.2.0 |
| indent-string | 5.0.0 | 4.0.0 |
Moved: 2 · 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
- No release in this window recorded a passing observation at PROJECT_TEST.
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.