CodeSampleX

Recordsnpm@jest/types29.6.3

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

Current conditions

@jest/types @29.6.3windows 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 (2)

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 5 · Steady 4

First observed break

29.6.3

linux · node@22.23 · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@jest/schemas 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 36 project-days
@types/node 26.2.0 CANDIDATE Correlated change; unproven combination contract passed 9 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 25 project-days
@types/istanbul-lib-coverage 2.0.6 PASS All observations passed contract passed 34 project-days
@types/istanbul-reports 3.0.4 PASS All observations passed contract passed 34 project-days
@types/yargs 17.0.35 PASS All observations passed contract passed 33 project-days
chalk 4.1.2 PASS All observations passed contract passed 38 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: 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.