CodeSampleX

Recordsnpmreact-dom19.2.0react-dom.flushSync

Change the conditions
Fixed
Runtimenode 24 Symbolreact-dom.flushSync
Filter OSwindows 11 Package version19.2.0 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

react-dom.flushSync @19.2.0windows 11 · x64 · node 24 · npm 11 · node

0 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
0 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-11-04
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

19.2.8

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

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

View exact conditions View failure cluster

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.819.0.018.3.118.2.0
scheduler 0.28.0 0.27.0 0.25.0 0.23.2 0.23.2
loose-envify — — — 1.4.0 1.4.0

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