Records/npm/react-dom/19.2.0/react-dom.flushSync

Compatibility matrix

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.

snapshot · 2026-11-04

Failure clusters

• observed PROJECT_TEST ELIFECYCLE Evidence gap ×10 18.3.1 → 19.2.0 → 19.2.8 executionContext=node · os=windows
  Evidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-21 · Last seen: 2026-11-04
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7 18.3.1 → 19.0.0 → 19.2.0 → 19.2.8 executionContext=node
  Evidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-18 · Last seen: 2026-11-03
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed PROJECT_TEST Evidence gap ×2 19.2.0 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 react-dom.flushSync
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-11-04 · Last seen: 2026-11-04
  Diagnostic re-verification candidate
  Where does this failure start and stop?