CodeSampleX

Recordsnpmjest-runtime

no sample at this coordinate yet

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version29.7.0
Filter Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters
OS × Runtime
1○ 22026-09-02
How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 19 · Steady 5

First observed break

29.7.0

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef

Library Version Health Measured there Projects
@jest/environment 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@jest/fake-timers 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@jest/globals 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@jest/source-map 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@jest/test-result 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
@jest/transform 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
@types/node 26.2.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 3 project-days
cjs-module-lexer 1.4.3 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
glob 7.2.3 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
jest-haste-map 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
jest-message-util 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
jest-mock 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
jest-regex-util 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
jest-resolve 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
jest-snapshot 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
jest-util 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
chalk 4.1.2 PASS All observations passed contract passed 8 project-days
collect-v8-coverage 1.0.3 PASS All observations passed contract passed 7 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 8 project-days
slash 3.0.0 PASS All observations passed contract passed 6 project-days
strip-bom 4.0.0 PASS All observations passed contract passed 3 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: 17 · 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.