Recordsnpmrollup4.63.1
Change the conditions
Current conditions
rollup @4.63.1ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 1 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
- 4 / 4
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @types/estree | 1.0.9 | 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 | 4.63.1 | 4.63.0 | 4.62.5 | 4.62.4 |
|---|---|---|---|---|
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 |
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 UNKNOWN exit 1 Evidence gap ×1 4.63.1 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8fd30f2a6304…fil<path>:<n> · throw new Error(errorMsg); · ^ · Error: Vitest failed to access its internal state.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