Recordsnpmplaywright
Change the conditions
Current conditions
playwright @1.61.0windows 11 · x64 · node 24 · npm 11 · node
0 of 18 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- nothing at this coordinate
- Contract verifications
- 0 / 18
- Usage records
- 76
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 18 passed
Verified — this network ran a contract at this coordinate.
-
playwright.chromium
0 of 18 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.61.0
windows · node@24.13 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:62b8752fd43c309f882b6017abf27dc1c24ac9b4232c9e7cd580f22d301eebb9
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| playwright-core | 1.61.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 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.
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.