Recordsnpmrollup4.67.5
Change the conditions
Current conditions
rollup @4.67.5windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
98 of 113 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 98 / 113
- Contract verifications
- nothing at this coordinate
- Usage records
- 32
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 15
- Last recorded
- 2026-11-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.62.4
executionContext=node
40 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
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.3 | 4.63.2 | 4.63.1 | 4.63.0 | 4.62.5 | 4.62.4 | 4.62.3 | 4.54.0 | 4.34.8 | 4.24.0 |
|---|---|---|---|---|---|---|---|---|---|---|
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.8 | 1.0.6 | 1.0.6 |
Moved: 1 · unchanged at every release: 0
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_TEST ELIFECYCLE Evidence gap ×20 4.62.3 → 4.62.4 → 4.63.1 → 4.67.5 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-21 · Last seen: 2026-11-18Diagnostic re-verification candidate
-
observed PROJECT_COMPILE Evidence gap ×2 4.67.5 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-11-18 · Last seen: 2026-11-18Diagnostic re-verification candidate