Recordsnpm@babel/helper-define-polyfill-provider1.0.0
Change the conditions
Current conditions
@babel/helper-define-polyfill-provider @1.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 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 failed
- Project observations
- 3 / 3
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.0.0 @babel/helper-compilation-targets@8.0.0
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:963dc79aa288c19eee01bb47568c83786a210bb952d8560eea6a22241495b6f7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-compilation-targets | 8.0.0 | FAIL Linked failure observed; version changed across releases | contract passed | 3 project-days |
| @babel/helper-plugin-utils | 8.0.1 | FAIL Linked failure observed; version changed across releases | contract passed | 3 project-days |
| lodash.debounce | 4.0.8 | FAIL Linked failure observed on this release | contract passed | 3 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.6.8 |
|---|---|---|
| @babel/helper-compilation-targets | 8.0.0 | 7.29.7 |
| @babel/helper-plugin-utils | 8.0.1 | 7.29.7 |
| debug | — | 4.4.3 |
| lodash.debounce | 4.0.8 | 4.0.8 |
| resolve | — | 1.22.12 |
Moved: 2 · unchanged at every release: 3
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_ASSERTION Evidence gap ×1 1.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:963dc79aa288…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Arrow function must be converted to function expressionnode · 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