Zipper Tools

ESLint Migration Guides

How to move .eslintignore patterns into flat config

Carry straightforward .eslintignore and ignorePatterns entries into flat config while keeping the hard cases explicit.

Start here

The safe first move

Move straightforward ignore patterns into the flat config ignores list. Stop when a pattern is negated or otherwise ambiguous.

Stop before automation when: Negated ignore patterns. Non-string ignorePatterns entries.

Target shape

module.exports = [
  {
    ignores: ["**/dist", "**/coverage"],
  },
];

Repo fit check

Want to know if your repo has this pattern?

Run the matching scanner locally first. The fit-report add-on is not listed for this proof-only product yet, so use the proof page and scanner output before treating it as a purchase candidate.

  • Local scan; no repository upload.
  • Supported findings are separated from manual-review findings.
  • Buy only when the repeated pattern is worth automating.
Run the static-config scan View example report See when to buy 
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewable

Why this page exists

How to move .eslintignore patterns into flat config

Simple ignore patterns are portable. Negated and malformed patterns are not.

Direct answer

What changes

Move straightforward ignore patterns into the flat config ignores list. Stop when a pattern is negated or otherwise ambiguous.

Example

Before and after

Before

dist/
coverage/

After

module.exports = [
  {
    ignores: ["**/dist", "**/coverage"],
  },
];

Decision path

If this repeats across the repo, open the evaluation pages next.

This product exists for the static-config subset. It does not pretend to evaluate JS config logic.

  • Teams migrating static .eslintrc JSON or YAML configs.
  • Repos that still store eslintConfig inside package.json.
  • The fit-report add-on is not listed for this proof-only product yet; use the proof page and scanner output before treating this as purchasable.

Before checkout

Product fit, proof, and price should all be one click away.

Current listed price is not published on the pricing page yet.

Typical symptoms

  • The repo still relies on .eslintignore or ignorePatterns.
  • The migration needs a clean carry-forward path for simple ignores.
  • Reviewers want to know which ignore rules stay safe and which do not.

What the product covers

  • Straightforward .eslintignore pattern normalization.
  • Straightforward ignorePatterns migration from static configs.
  • Cross-links to the negated-pattern manual bucket.

Manual-review boundary

  • Negated ignore patterns.
  • Non-string ignorePatterns entries.
  • Ignore logic bundled with unsupported JS config files.

Keep the migration narrow

Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.

FAQ

Fast answers before you decide

What is the safest fix for .eslintignore flat config?

Move straightforward ignore patterns into the flat config ignores list. Stop when a pattern is negated or otherwise ambiguous.

Can .eslintignore flat config be automated?

Automate only the supported subset: Straightforward .eslintignore pattern normalization. Straightforward ignorePatterns migration from static configs. Cross-links to the negated-pattern manual bucket. Keep these cases in manual review: Negated ignore patterns. Non-string ignorePatterns entries. Ignore logic bundled with unsupported JS config files.

When should I buy ESLint Flat Config Migration Cleanup Pack?

Use ESLint Flat Config Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Run the public scan or read the proof first. The fit-report add-on is not listed for this proof-only product yet; if unsupported findings dominate, keep the work manual.