サンプル

Differentiate React 18 react-dom/server stream controller architecture, renderToString Suspense fallback markup, and Node entrypoint boundary differences

sha256:b585a75e10818c9c7f8c2aebc3549f5069478f6a50a1a28cfc97be27ff7f8a69

PUBLISHED L3_CONTRACT_PASS MIT-0

ケース

ゴール: Differentiate React 18 react-dom/server stream controller architecture, renderToString Suspense fallback markup, and Node entrypoint boundary differences HOW
パッケージ: react-dom 18.3.1
環境: node
作成日: 2026-08-17T02:01:19Z

よくある思い込み

renderToPipeableStream returns a Node.js Readable stream or a Promise resolving to one, while renderToString throws when encountering suspended components

このサンプルの作者が、ここで開発者やモデルが期待するであろうこととして記録したもの。下の契約が実際に実行されたものだ。

コントラクト

renderToPipeableStream returns a synchronous { pipe, abort } controller object that is neither a Readable stream nor a Promise, where pipe(dest) returns the passed writable destination
Piping the stream controller into a Writable destination upon onShellReady emits the rendered HTML string synchronously
renderToString with a suspended component renders fallback HTML with diagnostic template markers instead of throwing or awaiting the promise
react-dom/server in Node retains deprecated renderToNodeStream but omits renderToReadableStream
react-dom retains legacy render and hydrate exports whereas modern createRoot and hydrateRoot reside in react-dom/client

ファイル

NOTES.md
csx.json
package-lock.json
package.json
test/contract.mjs

検証済みアーティファクトをダウンロード (tar.gz) — 契約が実行された正確なバイト列

オリジンシーダー

csx-seed

検証レシート

node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9