Environment

Node version: 20.18.1
npm version: 10.8.2
Local ESLint version: 9.28.0
Global ESLint version: -
Operating System: macOS

What parser are you using?

@typescript-eslint/parser

What did you do?

I'm running npx eslint . --debug, and going through the logs, and I see for each file:

  eslint:source-code-fixer Applying fixes +45ms
  eslint:source-code-fixer shouldFix parameter was false, not attempting fixes +0ms

Is it normal that it spends all of this time on a file when shouldFix is false? Is there a way to make the linting faster somehow here?

Is it doing this to tell me which problems are fixable, because I should be able to opt out of this, but not sure?

What did you expect to happen?

I expect the "Applying fixes" step to be skipped when not running with --fix.

What actually happened?

The time is still spent Applying fixes

Link to Minimal Reproducible Example

https://github.com/eslint/eslint/issues

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response