Recordsnpmreact19.0.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | 11 | |
|---|---|---|---|
| React.createContext | |||
| React.createRef | |||
| React.lazy | |||
| defaultProps | |||
| react-dom.useFormStatus | |||
| react.Children | 100%2 |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 5✓
|
MEDIUM | 4 +2 | 5 | 100% | 1 · 2✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 3✓
|
LOW | 4 +2 | 3 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓ 1✕
|
LOW | 2 | 0 | 50% | 1 | 2026-08-21 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-18 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 18.3.1 → 19.0.0 → 19.2.8 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-18 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×4 18.3.1 → 19.0.0 executionContext=node · os=linux · runtime=node@22.23 react.createElementEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_PROCESS Evidence gap ×1 19.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 react.useCallbackEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-21 · Last seen: 2026-08-21
Symbols
- react.Children 1
- react.cloneElement 2
- react.Children.count 1 1 of 1 runs passed
- react.createContext 1 shared ×2
- react.createElement 2
- react.createRef 1
- defaultProps 1 shared ×2 1 of 1 runs passed
- react.forwardRef 1
- react.isValidElement 1 shared ×2
- jsx 1
- react.lazy 1
- react.Children.map 1 1 of 1 runs passed
- react.memo 1
- react.Children.only 1 1 of 1 runs passed
- ref 1
- renderToString 1
- react.Children.toArray 1 1 of 1 runs passed
- useActionState 1 shared ×2
- react.useCallback
- useDeferredValue 1
- react-dom.useFormStatus 1 shared ×2 1 of 1 runs passed
- useOptimistic 1 shared ×2
- react.useState
- react.version