CodeSampleX

Recordsnpm@babel/helper-module-transforms7.29.7

Change the conditions
Fixed
Runtimenode 22 Symbolwhole package Package managerpnpm 10
Filter OSwindows 11 Package version7.29.7 Architecturex64 Execution contextnode Clear filters

Current conditions

@babel/helper-module-transforms @7.29.7windows 11 · x64 · node 22 · pnpm 10 · node

package-level total, not an API

11 of 14 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 (1)

Project observations
11 / 14
Contract verifications
nothing at this coordinate
Usage records
72
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-21
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@babel/helper-module-imports 7.29.7 contract passed 14 project-days
@babel/helper-validator-identifier 7.29.7 contract passed 28 project-days
@babel/traverse 7.29.7 contract passed 1 project-day
@babel/traverse 7.29.8 contract passed 28 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.

Library8.0.17.29.7
@babel/helper-module-imports 8.0.0 7.29.7
@babel/helper-validator-identifier 8.0.4 7.29.7
@babel/traverse 8.0.4 7.29.7

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.

Recent failure clusters