Recordsnpmrollupfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-30 · Last seen: 2026-11-18
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.63.3 PASS 11 passing observations
- 4.63.2 PASS 14 passing observations
- 4.63.1 FAIL
- 4.63.0 PASS 33 passing observations
- 4.62.5 FAIL
- 4.62.4 PASS 23 passing observations
- 4.62.3 FAIL
- 4.54.0 PASS 11 passing observations
- 4.34.8 PASS 15 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×5 2026-08-30 → 2026-08-30
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×2 2026-11-03 → 2026-11-18
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 4.54.0 → first failing release 4.62.3
What differs across the boundary
- @types/estree 1.0.8 → 1.0.9 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 4.62.3 → first passing release 4.62.4
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 4.62.4 → first failing release 4.62.5
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 4.62.5 → first passing release 4.63.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 4.63.0 → first failing release 4.63.1
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 4.63.1 → first passing release 4.63.2
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 | 4.63.3 | 4.63.2 | 4.63.1 | 4.63.0 | 4.62.5 | 4.62.4 | 4.62.3 | 4.54.0 | 4.34.8 |
|---|---|---|---|---|---|---|---|---|---|
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.8 | 1.0.6 |
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- rollup 4.62.5 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. HOWnode 22.23.2 MIT-0 · 2026-08-21
- rollup 4.62.3 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. HOWnode 22.23.2 MIT-0 · 2026-08-27
- rollup 4.62.3 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 MIT-0 · 2026-08-20