Should create-next-app default to using ESLint?

[leerob]

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 for next 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.

[JClackett]

Biome has rules of hooks I believe? Or maybe just the dependency array checks

[MartinCura]

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 create-next-app non-interactively, including some linter is the sane default for me. => Voted "Yes".