Recordsnpmrolldown1.2.4
Change the conditions
Current conditions
rolldown @1.2.4alpine musl · x64 · node 22 · npm · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.2.4
windows · node@24.13 · moduleSystem=esm · executionContext=node
1 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @oxc-project/types | 0.144.0 | CANDIDATE Correlated change; unproven combination | builds observed | 4 project-days |
| @rolldown/pluginutils | 1.0.1 | PASS All observations passed | contract passed | 4 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 | 1.2.8 | 1.2.7 | 1.2.6 | 1.2.4 |
|---|---|---|---|---|
| @oxc-project/types | 0.149.0 | 0.148.0 | 0.147.0 | 0.144.0 |
| @rolldown/pluginutils | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 |
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.