CodeSampleX

Recordsnpmjest-diff29.7.0

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

Current conditions

jest-diff @29.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 11 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
32 / 32
Contract verifications
0 / 11
Usage records
36
Independent reporting peers
2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
chalk 4.1.2 contract passed 8 project-days
diff-sequences 29.6.3 contract passed 6 project-days
jest-get-type 29.6.3 contract passed 5 project-days
pretty-format 29.7.0 contract passed 5 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
pretty-format 30.4.1 29.7.0
@jest/diff-sequences 30.4.0
@jest/get-type 30.1.0
chalk 4.1.2 4.1.2
diff-sequences 29.6.3
jest-get-type 29.6.3

Moved: 1 · unchanged at every release: 5

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