Recordsnpmreact-domfailure issue
Failure signature
PROJECT_TEST ELIFECYCLE Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-26
react-dom.createRoot
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 19.3.0 PASS 12 passing observations
- 19.2.8 FAIL
- 19.2.7 not measured
- 19.2.0 not measured
- 19.0.0 PASS 7 passing observations
- 18.3.1 FAIL
- 18.2.0 PASS 2 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@22.16 ×3 2026-08-24 → 2026-08-24
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 18.2.0 → first failing release 18.3.1
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 18.3.1 → first passing release 19.0.0
What differs across the boundary
- loose-envify — → 1.4.0 hypothesis
- scheduler 0.25.0 → 0.23.2 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release 19.0.0 → first failing release 19.2.8
Releases between them never measured at this stage: 2
What differs across the boundary
- scheduler 0.25.0 → 0.27.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 19.2.8 → first passing release 19.3.0
What differs across the boundary
- scheduler 0.28.0 → 0.27.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_TEST: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- react-dom 19.2.8: prerender This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWprerender MIT-0 · 2026-08-26
- react-dom 19.2.8: prerenderToNodeStream This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWprerenderToNodeStreamnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 19.2.8: createRoot This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreact-dom.createRootnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 18.3.1: Portal rendering into external DOM nodes and event bubbling with React 18 createPortal This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcreatePortalnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 18.3.1: createRoot This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreact-dom.createRootnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 18.3.1: Mount components with react-dom/client createRoot, manage updates, and unmount cleanly This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcreateRootreact-dom/client.createRootnode 22.23.2 MIT-0 · 2026-08-26