CodeSampleX

Recordsnpm@jest/console29.7.0

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

Current conditions

@jest/console @29.7.0debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (7)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 2

First observed break

29.7.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

4 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
@types/node 26.2.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@types/node 26.3.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@types/node 26.4.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@types/node 26.4.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
jest-message-util 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
jest-util 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
chalk 4.1.2 PASS All observations passed contract passed 18 project-days
slash 3.0.0 PASS All observations passed contract passed 18 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
@jest/types 30.4.1 29.6.3
@types/node 26.4.0 26.3.0
jest-message-util 30.4.1 29.7.0
jest-util 30.4.1 29.7.0
chalk 4.1.2 4.1.2
slash 3.0.0 3.0.0

Moved: 4 · 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