`eslint . --fix` Is the Command You Use When the Codebase Is Yelling About Style and You Want the Machine to Handle the Boring Part

Why this command matters: if the linter is complaining about a thousand mechanical issues, your time is usually better spent on the parts the machine cannot fix.

eslint . --fix is a workhorse command for JavaScript and TypeScript projects. It lets ESLint automatically correct many rule violations, which is especially useful after large refactors, dependency upgrades, or style-rule changes.

The command

npx eslint . --fix

This tells ESLint to scan the current project tree and apply automatic fixes where the rules support them.

That does not mean every lint issue disappears, but it does clear a lot of low-value manual cleanup.

What it is good for

It is especially useful when:

1. formatting-like lint issues exploded after a merge
2. import ordering and unused code warnings are piling up
3. a repo adopted stricter rules and needs bulk cleanup
4. you want to reduce noise before reviewing the real logic changes

The goal is not laziness. The goal is focusing human attention on the parts that still require judgment.

Final recommendation

If the linter is screaming about fixable issues, let it fix them. eslint . --fix is still one of the fastest ways to convert noisy mechanical lint debt into a cleaner codebase before you spend review energy on logic.

Sources

• ESLint command-line interface