CodeSampleX

Recordsnpm@jest/test-result29.7.0

Change the conditions
Fixed
Runtimenode 24
Filter OSwindows 11 Package version29.7.0 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@jest/test-result @29.7.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

1 of 1 passed

Observed — real project builds reported from this coordinate.

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

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

29.7.0

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:83bb774d036676c6450400f533510c87165d7879e817977fb7245a5acef3dd9f

Library Version Health Measured there Projects
@jest/console 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
@types/istanbul-lib-coverage 2.0.6 PASS All observations passed contract passed 13 project-days
collect-v8-coverage 1.0.3 PASS All observations passed contract passed 13 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: 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.