Package Exports

eslint-config-biome
eslint-config-biome/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-config-biome) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-config-biome

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

💿 Installation

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

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

import biome from "eslint-config-biome";

export default [
  // other configs,
  biome,
];

Or .eslintrc.* (eslint <= v8): Add the following as the last item in the "overrides" array. Create it if necessary.

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

ℹ️ Info

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

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

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

"scripts": {
  "lint": "biome check --unsafe --fix && eslint --fix .",
  "lint:check": "biome check --unsafe && eslint .",
}

This package includes eslint-config-prettier, so formatting rules are also disabled as Biome is equivalent to Prettier. Attribution.