@typescript-eslint/eslint-plugin 8.x
Use @typescript-eslint/eslint-plugin v8 exports, legacy preset names, rule definitions, typed-linting requirements, and v8 migration constraints.
- For
@typescript-eslint/eslint-plugin@8.70.0- Verified
- 2026-09-08, 3 examples executed
- Package
@modootoday/pmcp-typescript-eslint-eslint-plugin@8.0.0
What it covers
- What this package provides
- Configuration names: do not mix package shapes
- Rules
- Legacy `.eslintrc.*` setup
- Flat config and v8
- Typed linting
- v8 rule and configuration changes
- 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 plugin from '@typescript-eslint/eslint-plugin';
import assert from 'node:assert/strict';
assert.equal(typeof plugin.configs, 'object');
assert.equal(typeof plugin.rules, 'object');
assert.equal(typeof plugin.configs.recommended, 'object');
assert.equal(typeof plugin.rules['no-unused-vars'], 'object');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-eslint-pluginIt installs as a dev dependency of your project, and the MCP server finds it there like any other skill.