CodeSampleX

Recordsnpmreact-dom18.2.0react-dom.createRoot

Change the conditions
Fixed
Package version18.2.0 Symbolreact-dom.createRoot
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

react-dom.createRoot @18.2.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
1 / 1
Contract verifications
0 / 2
Independent reporting peers
1
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
loose-envify 1.4.0 contract passed 2 project-days
scheduler 0.23.2 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.2.819.0.018.3.118.2.0
scheduler 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