JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 30331
  • Score
    100M100P100Q147996F
  • License MIT

Disables all the ESLint rules that have a recommended and equivalent Biome rule

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

npm TypeScript PRs Welcome npm


Disables all the ESLint rules that have an equivalent and recommended Biome rule, so you can use both for better performance.

Early stage lib, will be improved soon with further possibilities such as considering non-recommended Biome rules.

đŸ’ŋ 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

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"

📰 Changelog