Recordsnpm@rollup/plugin-commonjs28.0.9
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | debian glibc | ubuntu glibc | |
|---|---|---|---|
| esmExternals | 100%1 | ||
| ignore | 100%1 | ||
| ignoreDynamicRequires | 100%1 | ||
| ignoreGlobal | 100%1 | ||
| ignoreTryCatch | 100%1 | ||
| requireReturnsDefault |
Showing the environments with the most evidence.
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.
Environment detail
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
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 1✓
|
LOW | 2 +1 | 1 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 5✓
|
LOW | 6 +3 | 5 | 100% | 1 · 1✓ | 2026-09-16 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-09-03 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 3✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: UNKNOWN 0✓ 2✕
|
ELEVATED FAILURE | 5 +2 | 2 | 71% | 1 | 2026-09-03 |
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×1 28.0.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:a064fa240004…node:internal/modules/esm/resolve:<n> · throw new ERR_MODULE_NOT_FOUND( · ^ · Error [ERR_MODULE_NOT_FOUND]: Cannot find module <str> imported from <path>npm · unclassified-diagnostic · outer npm test · 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.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:df5e9f844963…Contract failed: AssertionError [ERR_ASSERTION]: assert matching target resolves from dynamic module registry · at runContract (<url>) { …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
Symbols
- esmExternals 1 1 of 1 runs passed
- ignore 1 shared ×3 1 of 1 runs passed
- ignoreDynamicRequires 1 1 of 1 runs passed
- ignoreGlobal 1 1 of 1 runs passed
- ignoreTryCatch 1 1 of 1 runs passed
- requireReturnsDefault shared ×2 1 of 1 runs passed
- transformMixedEsModules shared ×2 1 of 1 runs passed