CodeSampleX

Recordsnpmreact-dom19.3.0

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

Current conditions

react-dom @19.3.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 22 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
64 / 75
Contract verifications
0 / 22
Usage records
60
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

19.3.0

windows · node@24.13 · moduleSystem=esm · executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
scheduler 0.28.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.

Library19.3.019.2.819.0.018.3.118.2.0
scheduler 0.28.0 0.27.0 0.25.0 0.23.2 0.23.2
loose-envify — — — 1.4.0 1.4.0

Moved: 1 · unchanged at every release: 1

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