Sample
Show which values from a React tree survive and which are dropped or reshaped by server stringification boundaries.
sha256:53d4afb16af1cea0fef82d0f97561097002440717618ddb62d5d5134f7928c04
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show which values from a React tree survive and which are dropped or reshaped by server stringification boundaries. HOW
- Packages
- react 19.2.8 react-dom 19.2.8
- Environment
- node
- Created
- 2026-08-17T03:18:20Z
Commonly assumed
Any React element rendered with react-dom/server should preserve all props and child boundaries in a stable textual shape.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert react-dom/server.renderToString inserts hydration separator comments for mixed renderable children where renderToStaticMarkup removes those separators.
- assert event-handler props, ref, key metadata, and false boolean host props are stripped from renderToString output.
- assert explicit HTML-host props and textual child data still round-trip as rendered attributes and text content.
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-17 · ed25519:d91480838ac982c9