Recordsnpmreact-dom18.2.0react-dom/test-utils.act
Change the conditions
Current conditions
react-dom/test-utils.act @18.2.0alpine musl · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 2 / 2
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-08-18
Evidence you can open
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 18.2.0 executionContext=node · os=linux · runtime=node@22.23 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 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