Recordsnpm@types/reactfailure issue
Failure signature
PROJECT_TEST ELIFECYCLE Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-26
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.18 FAIL
- 19.2.17 not measured
- 19.2.2 not measured
- 18.3.31 FAIL
- 18.3.26 PASS 1 passing observations
- 18.3.18 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@22.16 ×3 2026-08-21 → 2026-08-21
- 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.3.26 → first failing release 18.3.31
What differs across the boundary
- csstype 3.2.2 → 3.2.3 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.18 → first passing release 19.3.0
Both trees resolved every dependency to the same version. Nothing here moved.
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.18 | 18.3.31 | 18.3.26 | 18.3.18 |
|---|---|---|---|---|---|
| csstype | 3.2.3 | 3.2.3 | 3.2.3 | 3.2.2 | 3.2.3 |
| @types/prop-types | — | — | 15.7.15 | 15.7.15 | 15.7.15 |
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: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @types/react 19.2.18: useActionState 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. HOWuseActionStatenode 22.23.2 MIT-0 · 2026-08-23
- @types/react 19.2.18: useOptimistic 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. HOWuseOptimisticnode 22.23.2 MIT-0 · 2026-08-23
- @types/react 19.2.18 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 MIT-0 · 2026-08-23
- @types/react 18.3.31 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 MIT-0 · 2026-08-26