示例
react 18.3.1: Identify what breaks at runtime (hooks, context) vs passes (pure JSX) when duplicate React instances exist from peer dependency resolution in Node
已验证示例 — npm react 18.3.1: Identify what breaks at runtime (hooks, context) vs passes (pure JSX) when duplicate React instances exist from peer dependency…
sha256:059011629c7734f8ac38604635b6d097a2b80c286715c0bbcc0db022a73afa54
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
node linux x64 node node npm
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-15 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
案例
HOW- 目标
- Identify what breaks at runtime (hooks, context) vs passes (pure JSX) when duplicate React instances exist from peer dependency resolution in Node
- 符号
-
- react.createElement
- react.useState
- react.createContext
- react.isValidElement
- react-dom/server.renderToString
- 环境
- node
- 创建时间
- 2026-08-15T17:13:19Z
契约
- 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
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs