eslint-config-biome

Disables ESLint rules that have an equivalent and recommended Biome rule, allowing the simultaneous use of Biome and ESLint.

💿 Installation

1npm install -D eslint-config-biome # or your preferred package manager ;)

• .eslintrc.*: Add the following as the last item in the "overrides" array. Create it if necessary.

  1{
  2  "overrides": [
  3    // other overrides,
  4    {
  5      files: ["*.ts", "*.js", "*.tsx", "*.jsx"],
  6      extends: ["biome"],
  7    }
  8  ],
  9}

• Or eslint.config.js: Import eslint-config-biome and have it as the last item in the configuration array

  1import biome from "eslint-config-biome";
  2
  3export default [
  4  // other configs,
  5  biome,
  6];

ℹ️ Info

• In VSCode, to apply Biome and ESLint on save, you should have these in your project's .vscode/settings.json:

  1{
  2  "editor.codeActionsOnSave": {
  3    "source.fixAll.eslint": "explicit",
  4    "source.organizeImports.biome": "explicit",
  5    "quickfix.biome": "explicit"
  6  },
  7  "editor.defaultFormatter": "biomejs.biome"
  8}

• For package.json scripts and CI, I recommend running biome before eslint for faster failure detection.

  1"scripts": {
  2  "format:check": "biome check . && eslint .",
  3  "format": "biome check --apply-unsafe . && eslint --fix .",
  4}

• Since v1.4.0, this package includes eslint-config-prettier, so formatting rules are also disabled as Biome is equivalent to Prettier. Attribution.

• This package had its origin in this discussion.

📰 Changelog