CodeSampleX

Compatibilitynpmbabel-jest30.4.1

Change the conditions
Fixed
Package version30.4.1 Architecturex64
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

babel-jest @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 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
4 / 4
Contract verifications
0 / 2
Independent reporting peers
1
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@jest/transform 30.4.1 contract passed 2 project-days
@types/babel__core 7.20.5 contract passed 2 project-days
babel-plugin-istanbul 7.0.1 contract passed 2 project-days
babel-preset-jest 30.4.0 contract passed 2 project-days
chalk 4.1.2 contract passed 2 project-days
graceful-fs 4.2.11 contract passed 2 project-days
slash 3.0.0 contract passed 2 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.129.7.0
@jest/transform 30.4.1 29.7.0
babel-plugin-istanbul 7.0.1 6.1.1
babel-preset-jest 30.4.0 29.6.3
@types/babel__core 7.20.5 7.20.5
chalk 4.1.2 4.1.2
graceful-fs 4.2.11 4.2.11
slash 3.0.0 3.0.0

Moved: 3 · 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