CodeSampleX

Compatibilitynpm@eslint/eslintrc

there is a sample for this release and API (3)

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 version3.3.6
Filter Runtimenode 24 Symbolwhole package Execution contextnode Clear filters
Architecture × Package manager
1 12026-08-29
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
ajv 6.15.0 contract passed 3 project-days
debug 4.4.3 contract passed 3 project-days
espree 10.4.0 contract passed 3 project-days
globals 14.0.0 contract passed 3 project-days
ignore 5.3.2 contract passed 3 project-days
import-fresh 3.3.1 contract passed 3 project-days
js-yaml 4.3.1 contract passed 2 project-days
js-yaml 4.3.2 contract passed 1 project-day
minimatch 3.1.5 contract passed 3 project-days
strip-json-comments 3.1.1 contract passed 2 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.