CodeSampleX

Recordsnpmjest-runner30.4.2

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

Current conditions

jest-runner @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
@jest/console 30.4.1 contract passed 2 project-days
@jest/environment 30.4.1 contract passed 2 project-days
@jest/test-result 30.4.1 contract passed 2 project-days
@jest/transform 30.4.1 contract passed 2 project-days
@jest/types 30.4.1 contract passed 2 project-days
@types/node 26.4.0 contract passed 2 project-days
chalk 4.1.2 contract passed 2 project-days
emittery 0.13.1 contract passed 2 project-days
exit-x 0.2.2 contract passed 2 project-days
graceful-fs 4.2.11 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-haste-map 30.4.1 contract passed 2 project-days
jest-leak-detector 30.4.1 contract passed 2 project-days
jest-message-util 30.4.1 contract passed 2 project-days
jest-resolve 30.4.1 contract passed 2 project-days
jest-runtime 30.4.2 contract passed 2 project-days
jest-util 30.4.1 contract passed 2 project-days
jest-watcher 30.4.1 contract passed 2 project-days
jest-worker 30.4.1 contract passed 2 project-days
p-limit 3.1.0 contract passed 2 project-days
source-map-support 0.5.13 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/console 30.4.1 29.7.0
@jest/environment 30.4.1 29.7.0
@jest/test-result 30.4.1 29.7.0
@jest/transform 30.4.1 29.7.0
@jest/types 30.4.1 29.6.3
@types/node 26.4.0 26.2.0
jest-docblock 30.4.0 29.7.0
jest-environment-node 30.4.1 29.7.0
jest-haste-map 30.4.1 29.7.0
jest-leak-detector 30.4.1 29.7.0
jest-message-util 30.4.1 29.7.0
jest-resolve 30.4.1 29.7.0
jest-runtime 30.4.2 29.7.0
jest-util 30.4.1 29.7.0
jest-watcher 30.4.1 29.7.0
jest-worker 30.4.1 29.7.0
chalk 4.1.2 4.1.2
emittery 0.13.1 0.13.1
exit-x 0.2.2 —
graceful-fs 4.2.11 4.2.11
p-limit 3.1.0 3.1.0
source-map-support 0.5.13 0.5.13

Moved: 16 · unchanged at every release: 6

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