CodeSampleX

Recordsnpmchromium-bidi2.1.2

Change the conditions
Fixed
Runtimenode 24 Package version2.1.2
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

chromium-bidi @2.1.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

13 of 17 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (8)

Project observations
13 / 17
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Failures with a captured fingerprint
0 / 4
Last recorded
2026-08-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

2.1.2

moduleSystem=esm · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
mitt 3.0.1 PASS All observations passed contract passed 14 project-days
zod 3.25.76 PASS All observations passed contract passed 14 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.

Library17.0.214.0.02.1.21.3.0
mitt 3.0.1 3.0.1 3.0.1 3.0.1
zod 3.25.76 3.25.76 3.25.76 3.25.76

Moved: 0 · unchanged at every release: 2

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