Replies: 4 comments 3 replies
-
Biome has rules of hooks I believe? Or maybe just the dependency array checks |
Beta Was this translation helpful? Give feedback.
-
I think having a linter is a more sane default than not, especially in a React project. If Biome can do similar checks with hooks and such, then Eslint shouldn't necessarily be the first choice when choosing in the interactive CLI. But if someone's running |
Beta Was this translation helpful? Give feedback.
-
For someone without a strong opinion on linters then they're better off with ESLint than with no linter at all. The ESLint ecosystem is also still larger so it seems a more sensible default. Anyone who is opinionated enough to prefer Biome or prefer no linter at all is probably also experienced enough to remove ESLint and set up things the way they want them without this being too much of a big deal. What's wrong with config files other than people (and CEOs…) moaning about them on Twitter? I would prefer them all to be hidden away in a |
Beta Was this translation helpful? Give feedback.
-
Classic 50/50 poll response so far 😂 |
Beta Was this translation helpful? Give feedback.
-
Hey y'all. We're considering switching the default of
create-next-app
to not use ESLint.One reason to remove would be: fewer configuration files, and less things to remove. Notably, you can still pick ESLint during the
create-next-app
setup – it just wouldn't be the default. Another related bit is that we'd like to also support Biome fornext lint
in the future.One reason to keep ESLint as the default is that it gives you default checks around React development (e.g. hook usage), which could help beginners who are learning to build with React and Next.js.
127 votes ·
Beta Was this translation helpful? Give feedback.
All reactions