Sample
jsdom 26.1.0: Show that two sequential setState calls with stale state are not both applied in concurrent mode
Verified sample for npm jsdom 26.1.0: Show that two sequential setState calls with stale state are not both applied in concurrent mode. The contract ran on…
sha256:88f977ae74e5952e7ce178249ad2d13425490fd3043c1e33c2477d4095798122
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-17 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Show that two sequential setState calls with stale state are not both applied in concurrent mode
- Packages
- Symbols
-
- jsdom.JSDOM
- react.useState
- react-dom/client.createRoot
- react-dom/test-utils.act
- Environment
- node
- Created
- 2026-08-17T03:19:12Z
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