Recordsnpmbabel-plugin-polyfill-corejs30.14.2
Change the conditions
Current conditions
babel-plugin-polyfill-corejs3 @0.14.2debian glibc · 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
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.14.2
linux · node@22.23 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-define-polyfill-provider | 0.6.8 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| core-js-compat | 3.50.0 | PASS All observations passed | contract passed | 8 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.0.0 | 0.14.2 | 0.11.1 | 0.10.6 |
|---|---|---|---|---|
| @babel/helper-define-polyfill-provider | 1.0.0 | 0.6.8 | 0.6.8 | 0.6.8 |
| core-js-compat | 3.50.0 | 3.50.0 | 3.50.0 | 3.50.0 |
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×5 0.10.6 → 0.11.1 → 0.14.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.14.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:223705e02a51…ReferenceError: __dirname is not defined · at get version (fil<path>:<n>:<n>) · at main (<path>:<n>:<n>) · at Object.<anonymous> (<path>:<n>:<n>)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_AMBIGUOUS_MODULE_SYNTAX Evidence gap ×1 0.14.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:2e857e4a17a1…fil<path>:<n> · const { version } = JSON.parse(readFileSync(join(__dirname, <str>), <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 0.14.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: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