Sample
Show that two sequential setState calls with stale state are not both applied in concurrent mode
sha256:88f977ae74e5952e7ce178249ad2d13425490fd3043c1e33c2477d4095798122
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that two sequential setState calls with stale state are not both applied in concurrent mode HOW
- Packages
- jsdom 26.1.0 react 18.2.0 react-dom 18.2.0
- Environment
- node
- Created
- 2026-08-17T03:19:12Z
Commonly assumed
Two setState calls using the current state value will both increment the counter, resulting in a final state of 2
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert two sequential setCount(count + 1) calls in one React 18 concurrent-root update produce a final rendered state of 1
Files
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9