It sounds to me though that you formatted some huge file that wasn't previously formatted with prettier (vs your own changes) And that is annoying af. Just incredibly noisy if it's a bug fix. Propose your refactor but do it outside of a bug fix. More on reddit.com

I've installed Prettier extension in VS Code, and when I attempt to format a file, VS Code asked me: Do you want to format with the default formatter or with prettier formatter? I accidentally ch... More on stackoverflow.com

There should be a setting to format only the modified lines instead of the entire file. That way, all your new code will be autoformatted but you won't have all the unrelated changes. More on reddit.com

Because Prettier generally does a better job of formatting than ESLint. This is for three reasons: It's really fast, particularly in comparison to ESLint. Prettier is designed to format documents and that's it, which means it can be a lot simpler than ESLint, at least architecturally, especially as there's relatively little in the way of plugins. So if you just need to format your code quickly in one chunk, Prettier is the way to go. Prettier is already preconfigured, so it's also usually quicker to get started with. ESLint has some default formatting rules IIRC, but relatively minimal ones. To ensure every detail is formatted the same way, you need to put a lot of effort into configuring ESLint, which most people don't really want to do. Related: Conceptually, Prettier formats holistically, which is to say, it takes a whole document and applies its formatting to every single syntax node - generally, this means that you get very close to having exactly one valid output, no matter how the input file is formatted. ESLint, on the other hand, not only requires each formatting rule to be configured individually, but also applies them generally individually, so it's easier to have cases where you can get inconsistent behaviour depending on the original formatting of the file. More on reddit.com