CodeSampleX

Recordsnpmjest-message-util29.7.0jest-message-util.formatStackTrace

Change the conditions
Fixed
Symboljest-message-util.formatStackTrace
Filter OSubuntu glibc Runtimenode 22 Package version29.7.0 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

jest-message-util.formatStackTrace @29.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 7

First observed break

29.7.0

linux · node@22.23 · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
pretty-format 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
@babel/code-frame 7.29.7 PASS All observations passed contract passed 16 project-days
@types/stack-utils 2.0.3 PASS All observations passed contract passed 15 project-days
chalk 4.1.2 PASS All observations passed contract passed 17 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 17 project-days
micromatch 4.0.8 PASS All observations passed contract passed 15 project-days
slash 3.0.0 PASS All observations passed contract passed 16 project-days
stack-utils 2.0.6 PASS All observations passed contract passed 14 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.

Moved: 2 · unchanged at every release: 9

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