Compatibilitynpmreact-dom18.2.0react-dom.renderToString
Change the conditions
Current conditions
react-dom.renderToString @18.2.0ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 2 / 2
- Contract verifications
- 0 / 3
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| loose-envify | 1.4.0 | contract passed | 2 project-days |
| scheduler | 0.23.2 | contract passed | 2 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 19.2.8 | 19.0.0 | 18.3.1 | 18.2.0 |
|---|---|---|---|---|
| scheduler | 0.27.0 | 0.25.0 | 0.23.2 | 0.23.2 |
| loose-envify | — | — | 1.4.0 | 1.4.0 |
Moved: 1 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 18.2.0 executionContext=node · os=linux · runtime=node@22.23 react-dom.renderToString sha256:656e6214a177…Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 18.2.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 react-dom.renderToString sha256:47c28f8e8781…Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate