CodeSampleX

Recordsnpm@typescript-eslint/scope-manager8.66.0

Change the conditions
Fixed
Runtimenode 22 Package managerpnpm 10
Filter OSwindows 11 Package version8.66.0 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@typescript-eslint/scope-manager @8.66.0windows 11 · x64 · node 22 · pnpm 10 · node

package-level total, not an API

5 of 8 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 (1)

Project observations
5 / 8
Contract verifications
nothing at this coordinate
Usage records
62
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-21
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

8.66.0

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
@typescript-eslint/types 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@typescript-eslint/visitor-keys 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 9 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.69.08.68.08.67.08.66.08.65.08.46.4
@typescript-eslint/types 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4
@typescript-eslint/visitor-keys 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4

Moved: 2 · unchanged at every release: 0

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