Recordsnpm@rollup/plugin-commonjs
Change the conditions
Current conditions
@rollup/plugin-commonjs @29.0.3x64 · node 22 · npm · node
3 of 3 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 (2)
- Project observations
- 1 / 1
- Contract verifications
- 3 / 3
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
29.0.3
linux · node@22.23 · moduleSystem=cjs · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @rollup/pluginutils | 5.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| picomatch | 4.0.7 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| commondir | 1.0.1 | PASS All observations passed | contract passed | 4 project-days |
| estree-walker | 2.0.2 | PASS All observations passed | contract passed | 4 project-days |
| fdir | 6.5.0 | PASS All observations passed | contract passed | 4 project-days |
| is-reference | 1.2.1 | PASS All observations passed | contract passed | 4 project-days |
| magic-string | 0.30.21 | 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 | 29.0.3 | 28.0.9 | 28.0.7 | 28.0.2 | 28.0.1 |
|---|---|---|---|---|---|
| @rollup/pluginutils | 5.4.0 | 5.4.0 | 5.4.0 | 5.4.0 | 5.3.0 |
| picomatch | 4.0.7 | 4.0.7 | 4.0.7 | 4.0.7 | 4.0.3 |
| commondir | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 | 1.0.1 |
| estree-walker | 2.0.2 | 2.0.2 | 2.0.2 | 2.0.2 | 2.0.2 |
| fdir | 6.5.0 | 6.5.0 | 6.5.0 | 6.5.0 | 6.5.0 |
| is-reference | 1.2.1 | 1.2.1 | 1.2.1 | 1.2.1 | 1.2.1 |
| magic-string | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 | 0.30.21 |
| rollup | — | — | 4.34.8 | — | — |
Moved: 2 · unchanged at every release: 6
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.