Recordsnpm@types/react-domfailure issue
Failure signature
PROJECT_TEST exit 1 ELIFECYCLE ×10
ELIFECYCLE Test failed. See above for more details.
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer pnpm test · First recorded: 2026-08-29 · Last seen: 2026-09-01
sha256:7711694d48fa…
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 13 passing observations
- 19.2.4 FAIL
- 19.2.3 not measured
- 19.2.2 not measured
- 18.3.7 PASS 33 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×10 2026-08-29 → 2026-09-01
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.3.7 → first failing release 19.2.4
Releases between them never measured at this stage: 2
What differs across the boundary
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.4 → first passing release 19.3.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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.
Moved: 0 · unchanged at every release: 2
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
- Releases in this window never measured at PROJECT_TEST: 2
- No resolved dependency tree for 19.3.0 or for 19.2.4, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @types/react-dom 19.2.4: version 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. HOW@types/react-dom.version MIT-0 · 2026-08-26
- @types/react-dom 19.2.4: types 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. HOW@types/react-dom.typesnode 22.23.2 MIT-0 · 2026-08-26
- @types/react-dom 19.2.4: peerDependencies 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. HOW@types/react-dom.peerDependencies MIT-0 · 2026-08-26