Recordsnpmreact19.0.0React.lazy
Change the conditions
Current conditions
React.lazy @19.0.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
Dependency Health
Observed combinations and failure evidence for this release
First observed break
19.2.8
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 18.3.1 | 18.2.0 |
|---|---|---|
| loose-envify | 1.4.0 | 1.4.0 |
Moved: 0 · 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 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