Stop Running Prettier Through ESLint — Here's Why Standalone Is Better

If you've set up a JavaScript project in the last few years, there's a good chance you're running Prettier through eslint-plugin-prettier . It was the go-to approach for a while — one tool, one command, one unified set of squiggly red lines in your editor. Simple, right? Here's the thing: the Prettier team themselves recommend against it. And once you understand why, you'll probably want to change your setup too. Prettier Formats Way More Than JavaScript ESLint is a JavaScript (and TypeScript) tool. That's its world. When you run Prettier as an ESLint plugin, Prettier is confined to that world — it only gets invoked on files that ESLint processes. But Prettier natively supports a much broader set of languages: CSS, Less, and SCSS HTML JSON YAML Markdown (including MDX) GraphQL Vue and Angular templates Handlebars That package.json with inconsistent indentation? The .yaml config where someone mixed tabs and spaces? The CSS file with wildly different formatting conventions? ESLint never