Replaces Gatsby's ESLint Webpack configs, giving you full control to customize linting with the rules and developer experience you specifically need to maintain code quality.
This will COMPLETELY OVERWRITE any ESLint Webpack Plugins that Gatsby uses. The installation instructions will help you reactivate the two required rules as of writing:
npm install --save-dev gatsby-plugin-eslint eslint-webpack-plugin
or
yarn add --dev gatsby-plugin-eslint eslint-webpack-plugin
- Lints development mode in the
'develop'
stage. Add other Webpack Config Stages intostages
array to enable linting during other Gatsby stages (eg.build-javascript
) - Lint
.js
,.jsx
,.ts
, and.tsx
files. - Excludes
node_modules
,bower_components
,.cache
, andpublic
folders from linting - Otherwise uses
eslint-webpack-plugin
option defaults
-
Create
eslint.config.mjs
file in project root.export default [ { files: ['src/**/*.js'], rules: { 'no-anonymous-exports-page-templates': 'warn', 'limited-exports-page-templates': 'warn' } } ];
-
Add plugin into
gatsby-config.js
// gatsby-config.js const path = require('path'); // Get paths of Gatsby's required rules, which as of writing is located at // https://github.com/gatsbyjs/gatsby/tree/gatsby%405.3.3/packages/gatsby/src/utils/eslint-rules const gatsbyRequiredRules = path.join( process.cwd(), 'node_modules', 'gatsby', 'dist', 'utils', 'eslint-rules' ); module.exports = { plugins: [ // ...other plugins { resolve: 'gatsby-plugin-eslint', options: { configType: 'flat', eslintPath: 'eslint/use-at-your-own-risk', // Optional path for Gatsby required rules rulePaths: [gatsbyRequiredRules] // Default settings that may be omitted or customized // stages: ['develop'], // extensions: ['js', 'jsx', 'ts', 'tsx'], // exclude: ['node_modules', 'bower_components', '.cache', 'public'] } } ] };
-
Additionally as of writing, Gatsby's default ESLint config may be copied over if you would still like to take advavntage of those rules.
Mix and match your own ESLint plugins and rules depending on the React/Javascript/Typescript patterns you want to enforce. Here are three ways you can get started:
Basic React Linting with eslint-plugin-react
-
Follow
eslint-plugin-react
plugin installation procedures:npm install --save-dev eslint-plugin-react babel-eslint
or
yarn add --dev eslint-plugin-react babel-eslint
-
Add
.eslintrc
file to project root:{ "parser": "babel-eslint", // uses babel-eslint transforms "settings": { "react": { "version": "detect" // detect react version } }, "env": { "node": true // defines things like process.env when generating through node }, "extends": [ "eslint:recommended", // use recommended configs "plugin:react/recommended" ], "rules": { "no-anonymous-exports-page-templates": "warn", "limited-exports-page-templates": "warn" } }
Typescript Linting with ESLint Plugin Typescript
-
Follow
@typescript-eslint/eslint-plugin
plugin installation procedures:npm install --save-dev typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin
or
yarn add --dev typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin
-
Add
.eslintrc
file to project root:{ "extends": [ "eslint:recommended", "plugin:@typescript-eslint/recommended", ], "rules": { "no-anonymous-exports-page-templates": "warn", "limited-exports-page-templates": "warn" } }