Recordsnpmreact-dom18.3.1createRoot
shared with 2 packages — this evidence cannot say whose API it is
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- react-dom 18.3.1: Mount components with react-dom/client createRoot, manage updates, and unmount cleanly This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcreateRootreact-dom/client.createRootnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 18.3.1: createRoot This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreact-dom.createRootnode 22.23.2 MIT-0 · 2026-08-26
- react-dom 18.3.1: Differentiate React 18 react-dom/server stream controller architecture, renderToString Suspense fallback markup, and Node entrypoint boundary differences This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreact-dom/server.renderToPipeableStreamreact-dom/server.renderToStringreact-dom/server.renderToNodeStreamreact-dom/client.createRootreact-dom.rendernode MIT-0 · 2026-08-17
- react-dom 18.3.1: Differentiate React development vs production runtime contracts across NODE_ENV branching, jsxDEV stubbing, element immutability, and minified error invariant decoding This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreact.createElementreact/jsx-dev-runtime.jsxDEVreact/jsx-runtime.jsxreact.useLayoutEffectreact-dom/client.createRootreact-dom/server.renderToStringnode MIT-0 · 2026-08-16
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-26 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 4✓ — Verified: UNKNOWN 0✓ 3✕
|
ELEVATED FAILURE | 4 | 3 | 57% | 1 | 2026-08-30 |
| node 24.13 · TS · pnpm · windows
Observations: PROJECT_COMPILE 17✓ · PROJECT_TEST 15✓ 2✕
|
LOW | 34 | 0 | 94% | 1 | 2026-09-01 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 8✓ 34✕ · PROJECT_PROCESS 8✓ · PROJECT_TEST 16✓ 2✕ · PROJECT_TYPECHECK 6✓ 1✕ — Verified: UNKNOWN 0✓ 15✕
|
ELEVATED FAILURE | 75 | 15 | 42% | 1 | 2026-09-16 |
snapshot · 2026-09-16
Failure clusters
-
observed PROJECT_TEST ELIFECYCLE Evidence gap ×10 18.3.1 → 19.2.0 → 19.2.8 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-21 · Last seen: 2026-11-04Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7 18.3.1 → 19.0.0 → 19.2.0 → 19.2.8 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-18 · Last seen: 2026-11-03Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×6 18.3.1 → 19.0.0 executionContext=node · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-29 · Last seen: 2026-09-07Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 2 TS2307 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0470f88d95bb…lib/hooks/queries/index.ts(<n>,<n>): error TS2307: Cannot find module <str> or its corresponding type declarations. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:21025cd78572…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2561 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:5f96e966539e…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:7e077f646acc…lib/api/real-estate-statistics.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2551 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:8a1ebc675f2b…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2551: Property <str> does not exist on type <str>. Did you mean <str>? …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e51205820175…lib/api/real-estate-map-addresses.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×4 18.3.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e7aa54217e13…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed UNKNOWN exit 2 Evidence gap ×3 18.3.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:fddf8ea09045…Using CPython 3.12.3 interpreter at: <path> · Creating virtual environment at: .venv · error: Failed to create virtual environment …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-30Diagnostic re-verification candidate
Showing the 12 most-reported of 59 recorded failure clusters. The rest are single reports.