CodeSampleX

Recordsnpmplaywright1.63.0playwright.firefox

Change the conditions
Fixed
Symbolplaywright.firefox libcglibc
Filter OSubuntu glibc Runtimenode 22 Package version1.63.0 Architecturex64 Package managernpm 10 Execution contextnode Clear filters

Current conditions

playwright.firefox @1.63.0ubuntu glibc · x64 · node 22 · npm 10 · node

7 of 7 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
7 / 7
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-10
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

1.63.0

windows · node@24.13 · executionContext=node

3 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

View exact conditions View failure cluster
Library Version Health Measured there Projects
playwright-core 1.63.0 CANDIDATE Correlated change; unproven combination contract passed 11 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.