Compatibilitynpm@eslint/config-array0.19.2@eslint/config-array.ConfigArray
Change the conditions
Current conditions
@eslint/config-array.ConfigArray @0.19.2ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @eslint/object-schema | 2.1.7 | contract passed | 1 project-day |
| debug | 4.4.3 | contract passed | 1 project-day |
| minimatch | 3.1.5 | 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 | 0.23.5 | 0.21.2 | 0.19.2 |
|---|---|---|---|
| @eslint/object-schema | 3.0.5 | 2.1.7 | 2.1.7 |
| minimatch | 10.2.6 | 3.1.5 | 3.1.5 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 |
Moved: 2 · unchanged at every release: 1
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.