CodeSampleX

Recordsnpmreact-dom18.3.1createPortal

Change the conditions
Fixed
OSwindows 11 SymbolcreatePortal Architecturex64
Filter Runtimenode 24 Package version18.3.1 Package managernpm 11 Execution contextnode Clear filters

Current conditions

createPortal @18.3.1windows 11 · x64 · node 24 · npm 11 · node

8 of 10 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
8 / 10
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21

Dependencies

LibraryVersionMeasured thereProjects
loose-envify 1.4.0 contract passed 9 project-days
scheduler 0.23.2 contract passed 9 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.

Library19.2.819.0.018.3.118.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