Recordsnpmtypescript-eslint8.66.0tseslint.parser.parseForESLint
Change the conditions
Current conditions
tseslint.parser.parseForESLint @8.66.0alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-28
Dependency Health
Observed combinations and failure evidence for this release
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.
| Library | 8.66.0 | 8.65.0 |
|---|---|---|
| @typescript-eslint/eslint-plugin | 8.66.0 | 8.65.0 |
| @typescript-eslint/parser | 8.66.0 | 8.65.0 |
| @typescript-eslint/typescript-estree | 8.66.0 | 8.65.0 |
| @typescript-eslint/utils | 8.66.0 | 8.65.0 |
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
-
observed UNKNOWN exit 1 Evidence gap ×2 8.65.0 → 8.66.0 executionContext=node · os=linux · runtime=node@22.23 sha256:0bd98c410653…<path>:<n> · param.decorators.forEach(d => this.visit(d)); · ^ · TypeError: Cannot read properties of undefined (reading <str>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-05 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 8.66.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×1 8.66.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 Evidence gap ×1 8.66.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:e8e158b8a93f…<path>:<n> · node.implements.forEach(imp => this.visitType(imp)); · ^ · TypeError: Cannot read properties of undefined (reading <str>)node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05Diagnostic re-verification candidate