A jscodeshift-based codemod that runs ESLint against your codebase and adds eslint-disable-next-line comments for all existing violations, allowing gradual adoption of new rules. Current stable version is 3.0.2 (released under a new maintainer). Release cadence is sporadic, with major version bumps for breaking changes. Key differentiator: unlike manual rule disabling or lint suppressions, this automates the tedious process of adding suppression comments for legacy code, enabling teams to enable strict rules without immediate rewrites. Requires ESLint locally installed and Node >= 18.
npm install suppress-eslint-errorsVerified import paths — ran on the pinned version, not inferred.
Run the codemod to suppress all violations of eqeqeq and @typescript-eslint/no-explicit-any rules in JS/JSX files under ./src.
Update Node to >= 18 and reinstall suppress-eslint-errors.
When using --message, ensure it does not contain shell metacharacters or use quotes.
Remove --ignore-config from your command line.
Either change your ESLint config to treat the rule as an error (e.g., 'warn' -> 'error') or pass the rule IDs via --rules.
Review the output to ensure files are processed; if not, run without .gitignore handling by removing the file temporarily.
Use a legacy ESLint configuration format (e.g., .eslintrc) until flat config support is added.
Run 'npm install --save-dev eslint' or 'yarn add --dev eslint'.
Install jscodeshift as a dependency: 'npm install --save-dev jscodeshift' or run the tool via npx (it bundles jscodeshift internally).
Run ESLint directly first to identify problematic files, then exclude them or fix the syntax.
Provide one or more file/directory paths as positional arguments: 'npx suppress-eslint-errors ./src'.