CodeSampleX

Recordsnpmrecharts

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
OSwindows 11 Package version2.15.4
Filter Runtimenode 24 Package managernpm 11 Execution contextnode Clear filters
Architecture × Symbol
72026-09-01

Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

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 8 · Steady 0

First observed break

2.15.4

windows · node@24.13 · moduleSystem=cjs · executionContext=node

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
clsx 2.1.1 FAIL Linked failure observed on this release contract passed 1 project-day
eventemitter3 4.0.7 FAIL Linked failure observed on this release contract passed 1 project-day
lodash 4.17.21 FAIL Linked failure observed on this release contract passed 1 project-day
react-is 18.3.1 FAIL Linked failure observed on this release contract passed 1 project-day
react-smooth 4.0.4 FAIL Linked failure observed on this release contract passed 1 project-day
recharts-scale 0.4.5 FAIL Linked failure observed on this release contract passed 1 project-day
tiny-invariant 1.3.3 FAIL Linked failure observed on this release contract passed 1 project-day
victory-vendor 36.9.2 FAIL Linked failure observed on this release contract passed 1 project-day

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.