Recordsnpm@babel/plugin-transform-modules-amd8.0.1
Change the conditions
Current conditions
@babel/plugin-transform-modules-amd @8.0.1windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
6 of 6 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 6 / 6
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-16
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.0.1
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:963dc79aa288c19eee01bb47568c83786a210bb952d8560eea6a22241495b6f7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-module-transforms | 8.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| @babel/helper-plugin-utils | 8.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 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 | 8.0.1 | 7.29.7 |
|---|---|---|
| @babel/helper-module-transforms | 8.0.1 | 7.29.7 |
| @babel/helper-plugin-utils | 8.0.1 | 7.29.7 |
Moved: 2 · unchanged at every release: 0
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.