ixartz / Next-js-Boilerplate

🚀🎉📚 Boilerplate and Starter for Next.js 14+ with App Router and Page Router support, Tailwind CSS 3.4 and TypeScript ⚡️ Made with developer experience first: Next.js + TypeScript + ESLint + Prettier + Drizzle ORM + Husky + Lint-Staged + Vitest + Testing Library + Playwright + Storybook + Commitlint + VSCode + Netlify + PostCSS + Tailwind CSS ✨

Home Page:https://nextjs-boilerplate.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Why use so many overrides in ESLint?

kaushalyap opened this issue · comments

According to [.eslintrc](https://github.com/ixartz/Next-js-Boilerplate/blob/master/.eslintrc) there are a lot of overrides, why is that? Why not add extends and plugins directly?

Is there a lot to be overridden from following extends?

"airbnb-base",
"next/core-web-vitals", // Needed to avoid warning in next.js build: 'The Next.js plugin was not detected in your ESLint configuration'
"plugin:prettier/recommended"

You can avoid when you are using only one of them. But, this is needed when you try to make some dependencies working together. Some configuration from some dependencies are not working well together with their default configuration.