CodeSampleX

Recordsnpmbabel-plugin-jest-hoist29.6.3

Change the conditions
Fixed
Symbolwhole package Package managernpm
Filter OSalpine musl Runtimenode 22 Package version29.6.3 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

babel-plugin-jest-hoist @29.6.3alpine musl · x64 · node 22 · npm · node

package-level total, not an API

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
@babel/template 7.29.7 contract passed 4 project-days
@babel/types 7.29.8 contract passed 4 project-days
@types/babel__core 7.20.5 contract passed 4 project-days
@types/babel__traverse 7.28.0 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.

Library30.4.029.6.3
@babel/template 7.29.7
@babel/types 7.29.8
@types/babel__core 7.20.5 7.20.5
@types/babel__traverse 7.28.0

Moved: 0 · unchanged at every release: 4

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