Recordsnpmreact19.3.0react.useState
Change the conditions
Current conditions
react.useState @19.3.0windows 11 · x64 · node 24 · npm 11 · node
0 of 22 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 64 / 75
- Contract verifications
- 0 / 22
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
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 | 18.3.1 | 18.2.0 |
|---|---|---|
| loose-envify | 1.4.0 | 1.4.0 |
Moved: 0 · 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
-
observed PROCESS_START process start failed Evidence gap ×3 19.2.8 → 19.3.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 react.useState sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-13 · Last seen: 2026-09-16Diagnostic re-verification candidate