Recordsnpm@rollup/plugin-commonjs28.0.7commonjs
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- @rollup/plugin-commonjs 28.0.7: By default @rollup/plugin-commonjs renders external requires as default imports causing named exports to be inaccessible unless esmExternals is configured This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcommonjsesmExternalsnode MIT-0 · 2026-09-03
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 2✓
|
MEDIUM | 0 | 2 | 100% | 0 · 2✓ | 2026-08-18 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 1✓
|
LOW | 1 | 1 | 100% | 1 · 1✓ | 2026-09-15 |
snapshot · 2026-09-16
Failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 28.0.7 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:84b3f5326cf0…data:text/javascript;base64,<token>:<n> · throw new Error(<str>); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 28.0.7 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:b2da6dd25bdb…Contract failed: AssertionError [ERR_ASSERTION]: Values have same structure but are not reference-equal: · { · target: true · }node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×1 28.0.7 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c85f2eba559c…Contract failed: Error [ERR_MODULE_NOT_FOUND]: Cannot find package <str> imported from <path> …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate