CodeSampleX

Recordsnpm@rollup/plugin-commonjs28.0.7defaultIsModuleExports

Change the conditions
Fixed
SymboldefaultIsModuleExports
Filter OSdebian glibc Runtimenode 22 Package version28.0.7 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

defaultIsModuleExports @28.0.7debian glibc · x64 · node 22 · npm · node

1 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 came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 6

First observed break

28.0.7

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:84b3f5326cf037772e4c56ddbf91fbfae6012d0ace24abd875349c5952a58271

View exact conditions View failure cluster
Library Version Health Measured there Projects
@rollup/pluginutils 5.4.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
picomatch 4.0.7 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
commondir 1.0.1 PASS All observations passed contract passed 9 project-days
estree-walker 2.0.2 PASS All observations passed contract passed 9 project-days
fdir 6.5.0 PASS All observations passed contract passed 9 project-days
is-reference 1.2.1 PASS All observations passed contract passed 9 project-days
magic-string 0.30.21 PASS All observations passed contract passed 9 project-days
rollup 4.34.8 PASS All observations passed contract passed 1 project-day

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.

Library29.0.328.0.928.0.728.0.228.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.

Recent failure clusters