CodeSampleX

Recordsnpmreact-dom19.2.8react-dom.createPortal

Change the conditions
Fixed
Package version19.2.8 Symbolreact-dom.createPortal Execution contextnode
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm libcmusl Clear filters

Current conditions

react-dom.createPortal @19.2.8alpine musl · x64 · node 22 · npm · node

2 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 came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18
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.2.8

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

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
scheduler 0.27.0 CANDIDATE Correlated change; unproven combination contract passed 10 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