Recordsnpmeslint
there is a sample for this release and API (1)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @eslint-community/eslint-utils | 4.10.1 | contract passed | 1 project-day |
| @eslint-community/regexpp | 4.12.2 | contract passed | 1 project-day |
| @eslint/config-array | 0.21.2 | contract passed | 1 project-day |
| @eslint/config-helpers | 0.4.2 | contract passed | 1 project-day |
| @eslint/core | 0.17.0 | contract passed | 1 project-day |
| @eslint/eslintrc | 3.3.6 | contract passed | 1 project-day |
| @eslint/js | 9.39.5 | contract passed | 1 project-day |
| @eslint/plugin-kit | 0.4.1 | contract passed | 1 project-day |
| @humanfs/node | 0.16.8 | contract passed | 1 project-day |
| @humanwhocodes/module-importer | 1.0.1 | contract passed | 1 project-day |
| @humanwhocodes/retry | 0.4.3 | contract passed | 1 project-day |
| @types/estree | 1.0.9 | contract passed | 1 project-day |
| ajv | 6.15.0 | contract passed | 1 project-day |
| chalk | 4.1.2 | contract passed | 1 project-day |
| cross-spawn | 7.0.6 | contract passed | 1 project-day |
| debug | 4.4.3 | contract passed | 1 project-day |
| escape-string-regexp | 4.0.0 | contract passed | 1 project-day |
| eslint-scope | 8.4.0 | contract passed | 1 project-day |
| eslint-visitor-keys | 4.2.1 | 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.
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.
| Library | 10.9.1 | 10.9.0 | 9.39.5 |
|---|---|---|---|
| @eslint/config-array | 0.23.5 | 0.23.5 | 0.21.2 |
| @eslint/config-helpers | 0.7.0 | 0.7.0 | 0.4.2 |
| @eslint/core | 1.2.1 | 1.2.1 | 0.17.0 |
| @eslint/plugin-kit | 0.7.2 | 0.7.2 | 0.4.1 |
| eslint-scope | 9.1.2 | 9.1.2 | 8.4.0 |
| eslint-visitor-keys | 5.0.1 | 5.0.1 | 4.2.1 |
| @eslint-community/eslint-utils | 4.10.1 | 4.10.1 | 4.10.1 |
| @eslint-community/regexpp | 4.12.2 | 4.12.2 | 4.12.2 |
| @eslint/eslintrc | — | — | 3.3.6 |
| @eslint/js | — | — | 9.39.5 |
| @humanfs/node | 0.16.8 | 0.16.8 | 0.16.8 |
| @humanwhocodes/module-importer | 1.0.1 | 1.0.1 | 1.0.1 |
| @humanwhocodes/retry | 0.4.3 | 0.4.3 | 0.4.3 |
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 |
| ajv | 6.15.0 | 6.15.0 | 6.15.0 |
| chalk | — | — | 4.1.2 |
| cross-spawn | 7.0.6 | 7.0.6 | 7.0.6 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 |
| escape-string-regexp | 4.0.0 | 4.0.0 | 4.0.0 |
| espree | 11.2.0 | 11.2.0 | — |
| esquery | 1.7.0 | 1.7.0 | — |
| esutils | 2.0.3 | 2.0.3 | — |
| fast-deep-equal | 3.1.3 | — | — |
| file-entry-cache | 8.0.0 | — | — |
| find-up | 5.0.0 | — | — |
| glob-parent | 6.0.2 | — | — |
| ignore | 5.3.2 | — | — |
| imurmurhash | 0.1.4 | — | — |
| is-glob | 4.0.3 | — | — |
| json-stable-stringify-without-jsonify | 1.0.1 | — | — |
| minimatch | 10.2.6 | — | — |
| natural-compare | 1.4.0 | — | — |
| optionator | 0.9.4 | — | — |
Moved: 6 · unchanged at every release: 27
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.