CodeSampleX

Compatibilitynpm@jest/test-result30.4.1

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

Current conditions

@jest/test-result @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

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

Dependencies

LibraryVersionMeasured thereProjects
@jest/console 30.4.1 contract passed 2 project-days
@jest/types 30.4.1 contract passed 2 project-days
@types/istanbul-lib-coverage 2.0.6 contract passed 1 project-day
collect-v8-coverage 1.0.3 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/types 30.4.1 29.6.3
@types/istanbul-lib-coverage 2.0.6 2.0.6
collect-v8-coverage 1.0.3 1.0.3

Moved: 2 · unchanged at every release: 2

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