CodeSampleX

Recordsnpm@types/react19.2.18

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11
Filter OSwindows 11 Package version19.2.18 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@types/react @19.2.18windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

14 of 15 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
14 / 15
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

19.2.18

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
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.

Library19.3.019.2.1818.3.3118.3.2618.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.

Recent failure clusters