5.8.0 • Public • Published


Composable eslint config bases for my personal projects and others.

npm npm


  • Monorepo friendly: Each workspace can have its own config.
  • Composable: Compose your workspace eslint config from pre-defined bases.
  • Peace of mind: Plugins does not need to be installed per workspaces, thx to @rushstack/eslint-patch.
  • Performance!: Plugins enabled on file conventions patterns to increase perf.


Add the following devDependencies to workspace (apps/packages in monorepo) or main project package.json.

$ yarn add --dev eslint @belgattitude/eslint-config-bases

PS: To keep the size low, if you use the following plugins:

  • graphql: yarn add --dev @graphql-eslint/eslint-plugin
  • mdx: yarn add --dev eslint-plugin-mdx.
  • tailwind: yarn add --dev eslint-plugin-tailwindcss.

In one line

yarn add --dev @graphql-eslint/eslint-plugin \
               eslint-plugin-mdx \


Create an ./apps/my-app/.eslintrc.cjs file that extends any of the existing base configs. For example:

// next line only required if you're using a monorepo

module.exports = {
  root: true,
  parser: '@typescript-eslint/parser',
  parserOptions: {
    tsconfigRootDir: __dirname,
    project: "tsconfig.json",
  ignorePatterns: ["**/node_modules", "**/.cache", "build", ".next"],
  extends: [
    // Group 1: recommended always  
    "@belgattitude/eslint-config-bases/jest", // jest or similar (ie: vitest)
    // Group 2: Helps to avoid complexity (cyclomatic...)
    // Group 3: When working with react  
    // Group 4: Performance related (ie: set vs includes...)
    // Group 5: Various tools (per project)
    // '@belgattitude/eslint-config-bases/tailwind',  
    // "@belgattitude/eslint-config-bases/storybook",
    // "@belgattitude/eslint-config-bases/playwright",
    // "@belgattitude/eslint-config-bases/graphql-schema",
    // "@belgattitude/eslint-config-bases/mdx",  

    // Group 6: Framework specifics
    // ie:
    // - nextjs: 'next/core-web-vitals',
    // - remix:  '@remix-run/eslint-config',
    // ...

    // Group 7: Visual/Sort consistency  
    // Not recommended but can by applied on some projects
    // see https://github.com/azat-io/eslint-plugin-perfectionist
    // "@belgattitude/eslint-config-bases/perfectionist",
    // "@belgattitude/eslint-config-bases/perfectionist-jsx",

    // Group 8: Formatter  
    // Post configure the prettier base and run prettier
    // without conflicts thx to eslint-plugin-prettier
    // Alternatively to the above if you're already running prettier
    // we can get a speed up by using on eslint-prettier-config
    // "@belgattitude/eslint-config-bases/prettier-config",
  rules: {
    // Specific global rules for your app or package
    // Might help is next eslint plugin does not locate pages
    // https://nextjs.org/docs/messages/no-html-link-for-pages#pagesdir
    // '@next/next/no-html-link-for-pages': ['error', `${__dirname}/src/pages`],

    // https://typescript-eslint.io/rules/consistent-type-definitions/  
    // '@typescript-eslint/consistent-type-definitions': 'error'  
  overrides: [
    // Specific file rules for your app or package
      files: ['next.config.mjs'],
      rules: {
          'import/order': 'off',
          '@typescript-eslint/ban-ts-comment': 'off',
      files: ['tailwind.config.ts'],
      rules: {
          '@typescript-eslint/naming-convention': 'off',

Ensure your tsconfig.json includes the .eslintrc.cjs file:

  "exclude": ["**/node_modules", "**/.*/*"],
  "include": [
    ".eslintrc.*s", // <-- add this
    // rest of the includes


  • Prettier: @belgattitude/eslint-config-bases/prettier-plugin and @belgattitude/eslint-config-bases/prettier-config are mutually exclusives. Choose one. The prettier-config suppose that you run prettier independently. The prettier-plugin will run prettier for you. Easiest the prettier-plugin, fastest prettier-config (this mostly depends if you set up and persist caches as well)

  • Performance: Some rules are known to be slow (ie: import/namespace...). Slowest identified rules are disabled depending on context (ie: *.test.tsx? might not need everything). Depending on project it's possible to disable entirely some slow rules (ie: 'import/namespace': 'off'). A good tip run eslint with the TIMING=1 to identify slow rules.


You can find the bases in ./src/bases.

Base Match convention Scope
typescript all Naming conventions, consistent imports, import sorting...
sonar *.{js,jsx,ts,tsx} Keep levels of code complexity sane. (excl test and stories)
regexp *.{js,jsx,jsx,tsx} Keep regexp consistent and safer.
react *.{jsx,tsx} Recommendations for react, react-hooks and jsx projects.
react-query **/?(*.)+(test).{js,jsx,ts,tsx} Enforce "recommended" react-query usage.
jest **/?(*.)+(test).{js,jsx,ts,tsx} Catch inconsistencies or error in jest tests.
rtl **/?(*.)+(test).{js,jsx,ts,tsx} Potential errors / deprecations in react-testing-library tests.
graphql-schema *.graphql Ensure validity of graphql schema files.
mdx all Mdx validation
storybook *.stories.{ts,tsx,mdx} Potential errors / deprecations in stories.
playwright **/e2e/**/*.test.{js,ts} Keep "recommended" playwright usage.
prettier-plugin all Post configure eslint for prettier compatibility.


  • The order is important. Some bases will disable or tune previously defined rules. For example the react base will tune the naming conventions for function components and increase recommended cognitive complexity. The typescript base will also relax conventions for javascript files.

  • Based on filename conventions some rules are relaxed or disabled to avoid false positives and keep a good level of performance. For example the sonar base won't run on test and storybook files. If you work on different conventions the patterns must be updated.

Cyclic deps

Due to performance considerations the import/no-cycle isn't enabled by default. This rule can prevent subtle and hard to debug bugs. Depending on the project you can enable it either by setting and env variable ESLINT_IMPORT_NO_CYCLE=true yarn lint (will default to import/no-cycle: 2) or by adding it to the extended rules.

Prettier integration

Two ways to work with prettier.

  • @belgattitude/eslint-config-bases/prettier-plugin - eslint will run prettier under the hood
  • @belgattitude/eslint-config-bases/prettier-config - eslint will just disable some conflicting rules (so you'll need to run prettier after)

The first method is recommended for simplicity. For best perf use the cache option to run eslint.

Tune the behaviour by creating a config in .prettierrc.js

// @ts-check
const {
} = require("@belgattitude/eslint-config-bases/helpers");

 * @type {import('prettier').Config}
module.exports = {
  overrides: [
    // whatever you need

Tip: You can tune the provided prettier.base.config for your own needs.



Generic typescript project, mostly based on

Type/Plugin Comment
eslint:recommended The basics for code linting.
@typescript-eslint/recommended The basics for typescript.
@typescript-eslint/consistent-type Use TS 3.8+ imports/exports, helps with esbuild
eslint-plugin-import Order imports


Type/Plugin Comment
eslint-plugin-sonarjs/recommended Help to keep complexity sane


Type/Plugin Comment
eslint-plugin-jsx-a11y/recommended Helps to produce accessibility-ready jsx


Type/Plugin Comment
eslint-plugin-jest/recommended Jest recommended practices.

React Testing Library

Type/Plugin Comment
eslint-plugin-testing-library/recommended Ease when using react-testing-library


Type/Plugin Comment


To tune the behaviour, you can add setting in the top level config

module.exports = {
    settings: {
        'mdx/code-blocks': true,
        // optional, if you want to disable language mapper, set it to `false`
        // if you want to override the default language mapper inside, you can provide your own
        'mdx/language-mapper': {},





Package Sidebar


npm i @belgattitude/eslint-config-bases

Weekly Downloads






Unpacked Size

86.6 kB

Total Files


Last publish


  • s.vanvelthem