Recordsnpmreact-dom
Change the conditions
Current conditions
react-dom @19.2.8windows 11 · x64 · node 22 · npm 11 · node
13 of 14 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 (10)
- Project observations
- 13 / 14
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-19
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
13 of 14 passed
Observed — real project builds reported from this coordinate.
-
react-dom.createRoot
12 of 12 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
19.2.8
windows · node@24.13 · moduleSystem=esm · executionContext=node
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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.
| Library | 19.3.0 | 19.2.8 | 19.0.0 | 18.3.1 | 18.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.