rsnext/docs/basic-features/eslint.md

description
Next.js uses ESLint to find and resolve issues affecting the user or developer experience.

ESLint

Next.js uses ESLint to find and resolve issues affecting the user or developer experience. A minimal set of Next.js rules are provided by default, but can be extended by adding an .eslintrc file to your project.

Default configuration

By default, Next.js provides a set of recommended ESLint rules that are automatically linted against as part of next build. If you would like to control which ESLint rules are checked during builds, you will need to add an .eslintrc file to the root of your project.

Here's an example of an .eslintrc.json file:

{
  "extends": ["plugin:@next/next/recommended"],
  "parser": "@babel/eslint-parser",
  "parserOptions": {
    "requireConfigFile": false,
    "sourceType": "module",
    "babelOptions": {
      "presets": ["next/babel"]
    }
  }
}

• Extending the original base of rules (plugin:@next/next/recommended) is highly recommended to catch and fix significant Next.js issues in your application.
• Including @babel/eslint-parser with the next/babel preset ensures that all language features supported by Next.js will also be supported by ESLint. Although @babel/eslint-parser can parse TypeScript, consider using @typescript-eslint/parser if you have TypeScript enabled in your application to check for type-specific linting rules.

If you add an .eslintrc file to your application and don't include plugin:@next/next/recommendedin the config, its rules will not be checked during development or production builds. This is not recommended.

If you want to enable ESLint to run during development, or disable it for production builds; refer to the documentation for ESLint Warnings and Errors.