CodeSampleX

Recordsnpmplaywright1.61.0

Change the conditions
Fixed
Package version1.61.0 libcglibc
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

playwright @1.61.0ubuntu glibc · x64 · node 22 · npm 11 · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
88
Independent reporting peers
1
Last recorded
2026-09-01

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

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.

Library1.63.01.62.01.61.01.58.11.49.0
playwright-core 1.63.0 1.62.0 1.61.0 1.58.1 1.49.0

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.