Recordsnpm@babel/helper-module-transforms8.0.1@babel/helper-module-transforms.buildDynamicImport
Change the conditions
Current conditions
@babel/helper-module-transforms.buildDynamicImport @8.0.1ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-29
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-module-imports | 8.0.0 | CHANGED Version changed, no linked failure | 6 project-days | |
| @babel/helper-validator-identifier | 8.0.4 | CHANGED Version changed, no linked failure | 6 project-days | |
| @babel/traverse | 8.0.4 | CHANGED Version changed, no linked failure | 6 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 | 7.28.3 |
|---|---|---|---|
| @babel/helper-module-imports | 8.0.0 | 7.29.7 | 7.27.1 |
| @babel/helper-validator-identifier | 8.0.4 | 7.29.7 | 7.28.5 |
| @babel/traverse | 8.0.4 | 7.29.7 | 7.28.5 |
Moved: 3 · 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.