Recordsnpmtslibfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×8
expected: <path> \[ -z <str> \]; then\n\s+echo <str><path> · operator: <str>, · diff: <str> · }
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-17 · Last seen: 2026-09-17
sha256:6f5d744f31a0…
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.
- 2.8.1 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×8 2026-09-17 → 2026-09-17
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tslib 2.8.1: __assign, __rest, __spreadArray This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW__assign__rest__spreadArray__awaiter__values__read__importDefaultnode 22.23.2 MIT-0 · 2026-08-23