eslint-config-biome

Disables all the ESLint rules that have an equivalent and recommended Biome rule so you can use both of them ;)

💿 Installation

npm install -D eslint-config-biome

• .eslintrc.*: Add "biome" as the last item in the extends field.

{
  "extends": [
    "other-configs",
    "biome"
  ]
}

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

import eslintConfigBiome from "eslint-config-biome";

export default [
  otherConfigs,
  eslintConfigBiome,
];

ℹ️ Info

• In your .eslintrc, you can instead have this in overrides:

  "overrides": [{
    files: ["*.ts", "*.js", "*.tsx", "*.jsx"],
    extends: ["biome"],
  }],

  • Being it the last item in the array, this makes other existing overrides to have this patch applied. This also overrides any rules that may lie in the root of your .eslintrc under rules.

• You should use it together with eslint-config-prettier so formatting rules are also disabled as Biome has almost 100% compatibility with prettier. It may eventually be integrated into this package, so you won't need to also install it.

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

  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit",
    "source.organizeImports.biome": "explicit",
    "quickfix.biome": "explicit"
  },
  "editor.defaultFormatter": "biomejs.biome"

• Soon there will be a npx tool to disable ESLint rules based on your biome config file, so non-recommended biome rules will also be considered.

This package had its origin in this discussion. Thanks DaniGuardiola for your initial code!

📰 Changelog