CodeSampleX

Recordsnpmtypescript-eslint8.66.0config

Change the conditions
Fixed
Runtimenode 24 Symbolconfig
Filter OSwindows 11 Package version8.66.0 Architecturex64 Package managerpnpm 10 Execution contextnode Clear filters

Current conditions

config @8.66.0windows 11 · x64 · node 24 · pnpm 10 · node

0 of 229 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (2)

Project observations
294 / 390
Contract verifications
0 / 229
Independent reporting peers
1
Failures with a captured fingerprint
95 / 96
Last recorded
2026-09-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

8.66.0

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

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

Library Version Health Measured there Projects
@typescript-eslint/eslint-plugin 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@typescript-eslint/parser 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@typescript-eslint/typescript-estree 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@typescript-eslint/utils 8.66.0 CANDIDATE Correlated change; unproven combination contract passed 3 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.

Moved: 4 · 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

Showing the 12 most-reported of 158 recorded failure clusters. The rest are single reports.