Recordsnpmplaywright
Change the conditions
Current conditions
playwright @1.61.0windows 11 · x64 · node 24 · npm 11 · node
0 of 16 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 / 16
- Usage records
- 75
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 16 passed
Verified — this network ran a contract at this coordinate.
-
playwright.chromium
0 of 16 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| playwright-core | 1.61.0 | contract passed | 1 project-day |
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.
| Library | 1.62.0 | 1.61.0 | 1.58.1 |
|---|---|---|---|
| playwright-core | 1.62.0 | 1.61.0 | 1.58.1 |
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.