CodeSampleX

Recordsnpm@typescript-eslint/typescript-estree8.65.0

Change the conditions
Fixed
Package version8.65.0 Package managernpm 11
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@typescript-eslint/typescript-estree @8.65.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

8 of 10 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
8 / 10
Contract verifications
nothing at this coordinate
Usage records
12
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21

Dependencies

LibraryVersionMeasured thereProjects
@typescript-eslint/project-service 8.65.0 contract passed 4 project-days
@typescript-eslint/tsconfig-utils 8.65.0 contract passed 4 project-days
@typescript-eslint/types 8.65.0 contract passed 4 project-days
@typescript-eslint/visitor-keys 8.65.0 contract passed 4 project-days
debug 4.4.3 contract passed 4 project-days
minimatch 10.2.6 contract passed 4 project-days
semver 7.8.5 contract passed 4 project-days
tinyglobby 0.2.17 contract passed 4 project-days
ts-api-utils 2.5.0 contract passed 4 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.

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.

Library8.68.08.67.08.66.08.65.0
@typescript-eslint/project-service 8.68.0 8.67.0 8.66.0 8.65.0
@typescript-eslint/tsconfig-utils 8.68.0 8.67.0 8.66.0 8.65.0
@typescript-eslint/types 8.68.0 8.67.0 8.66.0 8.65.0
@typescript-eslint/visitor-keys 8.68.0 8.67.0 8.66.0 8.65.0
debug 4.4.3 4.4.3 4.4.3 4.4.3
minimatch 10.2.6 10.2.6 10.2.6 10.2.6
semver 7.8.5 7.8.5 7.8.5 7.8.5
tinyglobby 0.2.17 0.2.17 0.2.17 0.2.17
ts-api-utils 2.5.0 2.5.0 2.5.0 2.5.0

Moved: 4 · unchanged at every release: 5

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.

Recent failure clusters