eslint-plugin-testing-library 7.x

Practical guidance for eslint-plugin-testing-library ^7.0.0, including v7 compatibility requirements, legacy and flat ESLint configuration, available rules, customization settings, and common migration mistakes.

For

eslint-plugin-testing-library@7.16.2

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-eslint-plugin-testing-library@7.0.0

What it covers

• What this package is
• Configuration shapes
• Flat config
• Legacy `.eslintrc` config
• Rules
• Custom utilities and queries
• Migration traps
• Do not copy removed v6-era rule names
• Do not treat v7 as a runner
• Standalone package-surface checks
• 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';

const testingLibrary = require('eslint-plugin-testing-library');

assert.equal(typeof testingLibrary, 'object');
assert.equal(typeof testingLibrary.rules, 'object');
assert.equal(typeof testingLibrary.configs, 'object');
assert.equal(typeof testingLibrary.rules['await-async-queries'], 'object');
assert.equal(typeof testingLibrary.rules['no-debugging-utils'], 'object');

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. This is what happened, quoted from the run. The full ledger lists every package examined, including the ones that never became a skill.

• prepare: husky || true the package
• prepare: husky || true the package

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-eslint-plugin-testing-library

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