Sample
Identify what breaks at runtime (hooks, context) vs passes (pure JSX) when duplicate React instances exist from peer dependency resolution in Node
sha256:059011629c7734f8ac38604635b6d097a2b80c286715c0bbcc0db022a73afa54
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Identify what breaks at runtime (hooks, context) vs passes (pure JSX) when duplicate React instances exist from peer dependency resolution in Node HOW
- Packages
- react 18.3.1 react-dom 18.3.1
- Environment
- node
- Created
- 2026-08-15T17:13:19Z
Contract
- assert duplicate React modules share Symbol.for('react.element') enabling cross-instance element validation and stateless SSR
- assert duplicate React modules maintain isolated ReactSharedInternals causing hook dispatcher to be null during SSR and throwing TypeError on useState
- assert duplicate React createContext instances fail context propagation silently due to referential inequality across copies
- assert unifying peer dependency resolution to a shared module instance restores hook execution and context propagation
Files
- NOTES.md
- 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-15 · ed25519:d91480838ac982c9