CodeSampleX

Recordsnpmpuppeteer-core24.4.0puppeteer.connect

Change the conditions
Fixed
Symbolpuppeteer.connect
Filter OSalpine musl Runtimenode 22 Package version24.4.0 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

puppeteer.connect @24.4.0alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (3)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-23
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 3

First observed break

24.4.0

moduleSystem=esm · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
@puppeteer/browsers 2.8.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
chromium-bidi 2.1.2 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
devtools-protocol 0.0.1413902 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
debug 4.4.3 PASS All observations passed contract passed 9 project-days
typed-query-selector 2.12.2 PASS All observations passed contract passed 8 project-days
ws 8.21.3 PASS All observations passed contract passed 8 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Library25.7.024.43.124.4.024.2.1
@puppeteer/browsers 3.2.0 2.13.2 2.8.0 2.7.1
chromium-bidi 17.0.2 14.0.0 2.1.2 1.3.0
devtools-protocol 0.0.1666840 0.0.1608973 0.0.1413902 0.0.1402036
webdriver-bidi-protocol 0.4.2 0.4.1 — —
debug — 4.4.3 4.4.3 4.4.3
typed-query-selector 2.12.2 2.12.2 2.12.2 2.12.2
ws 8.21.3 8.21.3 8.21.3 8.21.3

Moved: 4 · unchanged at every release: 3

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.

Recent failure clusters