CodeSampleX

Recordsnpm@jest/reporters30.4.1

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

Current conditions

@jest/reporters @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
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@bcoe/v8-coverage 0.2.3 contract passed 1 project-day
@jest/console 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
@jridgewell/trace-mapping 0.3.31 contract passed 1 project-day
@types/node 26.4.0 contract passed 2 project-days
chalk 4.1.2 contract passed 2 project-days
collect-v8-coverage 1.0.3 contract passed 1 project-day
exit-x 0.2.2 contract passed 2 project-days
glob 10.5.0 contract passed 1 project-day
graceful-fs 4.2.11 contract passed 2 project-days
istanbul-lib-coverage 3.2.2 contract passed 1 project-day
istanbul-lib-instrument 6.0.3 contract passed 1 project-day
istanbul-lib-report 3.0.1 contract passed 1 project-day
istanbul-lib-source-maps 5.0.6 contract passed 1 project-day
istanbul-reports 3.2.0 contract passed 1 project-day
jest-message-util 30.4.1 contract passed 2 project-days
jest-util 30.4.1 contract passed 1 project-day
jest-worker 30.4.1 contract passed 1 project-day
slash 3.0.0 contract passed 1 project-day
string-length 4.0.2 contract passed 1 project-day
v8-to-istanbul 9.3.0 contract passed 1 project-day

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/console 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
glob 10.5.0 7.2.3
istanbul-lib-source-maps 5.0.6 4.0.1
jest-message-util 30.4.1 29.7.0
jest-util 30.4.1 29.7.0
jest-worker 30.4.1 29.7.0
@bcoe/v8-coverage 0.2.3 0.2.3
@jridgewell/trace-mapping 0.3.31 0.3.31
chalk 4.1.2 4.1.2
collect-v8-coverage 1.0.3 1.0.3
exit — 0.1.2
exit-x 0.2.2 —
graceful-fs 4.2.11 4.2.11
istanbul-lib-coverage 3.2.2 3.2.2
istanbul-lib-instrument 6.0.3 6.0.3
istanbul-lib-report 3.0.1 3.0.1
istanbul-reports 3.2.0 3.2.0
slash 3.0.0 3.0.0
string-length 4.0.2 4.0.2
strip-ansi — 6.0.1
v8-to-istanbul 9.3.0 9.3.0

Moved: 10 · unchanged at every release: 15

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