Recordsnpmpuppeteer-corefailure issue
Failure signature
PROJECT_TEST ENOENT Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-18 · Last seen: 2026-08-18
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=esm · os=windows · runtime=node@24.13 ×1 2026-08-18 → 2026-08-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 failing release 23.11.1 → first passing release 24.4.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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 | 24.43.1 | 24.4.0 | 24.2.1 |
|---|---|---|---|
| @puppeteer/browsers | 2.13.2 | 2.8.0 | 2.7.1 |
| chromium-bidi | 14.0.0 | 2.1.2 | 1.3.0 |
| devtools-protocol | 0.0.1608973 | 0.0.1413902 | 0.0.1402036 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 |
| typed-query-selector | 2.12.2 | 2.12.2 | 2.12.2 |
| webdriver-bidi-protocol | 0.4.1 | — | — |
| ws | 8.21.3 | 8.21.3 | 8.21.3 |
Moved: 3 · unchanged at every release: 4
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.
- Releases in this window never measured at PROJECT_TEST: 2
- No resolved dependency tree for 24.4.0 or for 23.11.1, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.