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 all the ESLint rules that have an equivalent and recommended Biome rule so that you can use both of them ;)

💿 Installation

npm install -D eslint-plugin-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 this the last item in the array, this will make sure that other existing overrides before it will 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 a 100% compatibility with prettier! You certainly no longer require prettier if you are using Biome.
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"

This package had its origin in this discussion.

Thanks DaniGuardiola for your initial code!