Sample
Differentiate React development vs production runtime contracts across NODE_ENV branching, jsxDEV stubbing, element immutability, and minified error invariant decoding
sha256:a8e74b80a92c127ce2b29ee4d261faaea5cb092cc5869188facceec927b1a737
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Differentiate React development vs production runtime contracts across NODE_ENV branching, jsxDEV stubbing, element immutability, and minified error invariant decoding HOW
- Packages
- react 18.3.1 react-dom 18.3.1
- Environment
- node
- Created
- 2026-08-16T12:42:21Z
Contract
- assert NODE_ENV non-production values (staging, test, undefined) strictly default to development bundles with frozen element props
- assert react/jsx-dev-runtime exports jsxDEV as undefined in production and throws TypeError when invoked by dev-compiled builds
- assert element and props immutability via Object.freeze is enforced in development but stripped in production enabling in-place mutation
- assert ReactDOMClient invariant errors format with human-readable explanations in development but compress into minified URL error codes in production
- assert SSR diagnostic warnings for client-only hooks (useLayoutEffect) log to console.error in development and are completely eliminated in production
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-16 · ed25519:d91480838ac982c9