Recordsnpm@types/react19.2.18useOptimistic
Change the conditions
Current conditions
useOptimistic @19.2.18alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-23
Dependency Health
Observed combinations and failure evidence for this release
First observed break
19.2.18
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| csstype | 3.2.3 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.