This is a good moment to think again about our eslint and prettier configuration so it is as simple as possible. Eslint We were following eslint-airbnb in the past, but I’d like our configuration to be as simple and as standard as possible. In the past, when prettier didn’t exist, eslint ... More on community.frontity.org

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

Migrating from 8.57.0 to 9.0.0 is a pain in the freaking ass Most companies will simply never migrate. I know of places that only just upgraded from like node 4 to 16. Takes 20 plugins to make everything play nicely ... It can be(I have never had huge issues) but once its set up theres rarely a reason to ever change it. Go for a modern library like biomejs that does the job of all the 25 plugins from ESLint in one super duper light and tightly wrapped package Theres no guarantee that it does what every company needs. Yeah having 50 plugins can be annoying but it also means you can tune the package to your exact needs. I personally prefer the Go style of just having the language dictate everything but that ship has sailed in the JS world for now. And did I mention the part where it is 30 times faster than ESLint and Prettier Thats only noticeable if you are formatting an entire project with tens of thousands of lines of code. Even on a large 1-2k line file ive never had prettier or eslint feel anything less than instant. Less technical debt Less code bloat True, having everything in one package with little configs does make things cleaner. Super fast performance on linting And how about less CI/CD bills? You can setup your CI to run linting on only changed files if thats a real issue. Generally linting is not the thing slowing your CI down, tests are going to be several magnitude slower. The time it takes to lint is a rounding error. I have a big personal project coming up so ill definitely check out biomejs. Its just going to be an incredibly tough sell for any company with like 10+ devs. Why change what already works, configuration that no one has had to touch in a year? More on reddit.com

Did you try this ? https://github.com/prettier/eslint-plugin-prettier?tab=readme-ov-file#configuration-new-eslintconfigjs I didn't upgrade yet to eslint 9, I dont know exactly how the new config works More on reddit.com