示例
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) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9