CodeSampleX

Recordsnpm@jest/transform

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 Package managernpm 10
Filter Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters
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.

Dependencies

LibraryVersionMeasured thereProjects
@babel/core 7.29.7 contract passed 6 project-days
@jest/types 29.6.3 contract passed 7 project-days
@jridgewell/trace-mapping 0.3.31 contract passed 7 project-days
babel-plugin-istanbul 6.1.1 contract passed 6 project-days
chalk 4.1.2 contract passed 7 project-days
convert-source-map 2.0.0 contract passed 6 project-days
fast-json-stable-stringify 2.1.0 contract passed 6 project-days
graceful-fs 4.2.11 contract passed 6 project-days
jest-haste-map 29.7.0 contract passed 6 project-days
jest-regex-util 29.6.3 contract passed 6 project-days
jest-util 29.7.0 contract passed 7 project-days
micromatch 4.0.8 contract passed 6 project-days
pirates 4.0.7 contract passed 6 project-days
slash 3.0.0 contract passed 6 project-days
write-file-atomic 4.0.2 contract passed 5 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.