CodeSampleX

Recordsnpmreact-dom18.3.1react-dom.Root

Change the conditions
Fixed
Symbolreact-dom.Root
Filter OSwindows 11 Runtimenode 24 Package version18.3.1 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

react-dom.Root @18.3.1windows 11 · x64 · node 24 · npm 11 · node

0 of 4 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
13 / 47
Contract verifications
0 / 4
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

18.3.1

windows · executionContext=node

7 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
scheduler 0.23.2 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
loose-envify 1.4.0 PASS All observations passed contract passed 13 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

Showing the 12 most-reported of 31 recorded failure clusters. The rest are single reports.