CodeSampleX

Recordsnpmjest-config30.4.2

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

Current conditions

jest-config @30.4.2ubuntu 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
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@babel/core 7.29.7 contract passed 2 project-days
@jest/get-type 30.1.0 contract passed 2 project-days
@jest/pattern 30.4.0 contract passed 2 project-days
@jest/test-sequencer 30.4.1 contract passed 2 project-days
@jest/types 30.4.1 contract passed 2 project-days
babel-jest 30.4.1 contract passed 2 project-days
chalk 4.1.2 contract passed 2 project-days
ci-info 4.4.0 contract passed 2 project-days
deepmerge 4.3.1 contract passed 2 project-days
glob 10.5.0 contract passed 2 project-days
graceful-fs 4.2.11 contract passed 2 project-days
jest-circus 30.4.2 contract passed 2 project-days
jest-docblock 30.4.0 contract passed 2 project-days
jest-environment-node 30.4.1 contract passed 2 project-days
jest-regex-util 30.4.0 contract passed 2 project-days
jest-resolve 30.4.1 contract passed 2 project-days
jest-runner 30.4.2 contract passed 2 project-days
jest-util 30.4.1 contract passed 2 project-days
jest-validate 30.4.1 contract passed 2 project-days
parse-json 5.2.0 contract passed 2 project-days
pretty-format 30.4.1 contract passed 2 project-days
slash 3.0.0 contract passed 2 project-days
strip-json-comments 3.1.1 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.229.7.0
@jest/test-sequencer 30.4.1 29.7.0
@jest/types 30.4.1 29.6.3
babel-jest 30.4.1 29.7.0
ci-info 4.4.0 3.9.0
glob 10.5.0 7.2.3
jest-circus 30.4.2 29.7.0
jest-environment-node 30.4.1 29.7.0
jest-regex-util 30.4.0 29.6.3
jest-resolve 30.4.1 29.7.0
jest-runner 30.4.2 29.7.0
jest-util 30.4.1 29.7.0
jest-validate 30.4.1 29.7.0
pretty-format 30.4.1 29.7.0
@babel/core 7.29.7 7.29.7
@jest/get-type 30.1.0 —
@jest/pattern 30.4.0 —
chalk 4.1.2 4.1.2
deepmerge 4.3.1 4.3.1
graceful-fs 4.2.11 4.2.11
jest-docblock 30.4.0 —
jest-get-type — 29.6.3
micromatch — 4.0.8
parse-json 5.2.0 5.2.0
slash 3.0.0 3.0.0
strip-json-comments 3.1.1 3.1.1

Moved: 13 · unchanged at every release: 12

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