CodeSampleX

Recordsnpmreact-dom19.0.0react-dom.flushSync

Change the conditions
Fixed
OSdebian glibc Symbolreact-dom.flushSync Execution contextnode
Filter Runtimenode 22 Package version19.0.0 Architecturex64 Package managernpm libcglibc Clear filters

Current conditions

react-dom.flushSync @19.0.0debian glibc · 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
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.0.0

executionContext=node

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
scheduler 0.25.0 CANDIDATE Correlated change; unproven combination contract passed 13 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.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