@typescript-eslint/parser 8.x

Use @typescript-eslint/parser ^8.0.0 directly or as the parser behind ESLint. Covers standalone parsing, complete parse results, isolated parser options, v8 Project Service naming, and boundaries around type-aware parsing.

For

@typescript-eslint/parser@8.70.0

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-typescript-eslint-parser@8.0.0

What it covers

• Direct parsing
• `parseForESLint`
• Isolated parsing with `withoutProjectParserOptions`
• Project-backed parsing
• v8 configuration mistake: Project Service spelling
• ESLint integration
• Other exports
• Does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import * as assert from 'node:assert/strict';
import * as parser from '@typescript-eslint/parser';

const ast = parser.parse('let x: number = 1;', {
  filePath: 'example.ts',
});

assert.equal(ast.type, 'Program');
assert.equal(ast.body.length, 1);
assert.equal(ast.body[0].type, 'VariableDeclaration');
assert.equal(ast.body[0].declarations[0].id.type, 'Identifier');
assert.equal(ast.body[0].declarations[0].id.typeAnnotation.type, 'TSTypeAnnotation');

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-typescript-eslint-parser

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.