typescript-eslint 8.x

Use typescript-eslint v8's unified flat-config package, extension lists, presets, and typed-linting configuration. Avoid carrying forward the split-package or legacy ESLint configuration shape unless the project explicitly uses legacy config.

For

typescript-eslint@8.70.0

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-typescript-eslint@8.0.0

What it covers

• Use the unified package first
• File extensions and globs
• Main package exports
• Typed linting
• Parser utilities
• Legacy configuration warning
• What this skill 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 assert from 'node:assert/strict';
import tseslint from 'typescript-eslint';

assert.deepEqual(tseslint.extensions.ts, ['mts', 'ts', 'cts', 'tsx']);
assert.deepEqual(tseslint.extensions.js, ['mjs', 'js', 'cjs', 'jsx']);
assert.deepEqual(
  [...tseslint.extensions.jsts].sort(),
  ['mjs', 'js', 'cjs', 'jsx', 'mts', 'ts', 'cts', 'tsx'].sort(),
);

const customGlob = `src/**/*.{${tseslint.extensions.ts.join(',')}}`;
assert.equal(customGlob, 'src/**/*.{mts,ts,cts,tsx}');

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

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