biome migrate eslint: Import ESLint Config
biome migrate eslint reads your existing ESLint configuration and writes the equivalent settings into biome.json.
When moving off ESLint you do not have to rebuild rule choices by hand. migrate eslint maps what it can and tells you what it could not.
What it does
biome migrate eslint loads the ESLint configuration it finds (including extended shareable configs) and updates biome.json with the closest matching Biome rules. It only changes the file with --write; without it the command reports what it would do.
Common usage
# preview the migration
npx @biomejs/biome migrate eslint
# write the result into biome.json
npx @biomejs/biome migrate eslint --write
# also map rules Biome considers "inspired by" ESLint
npx @biomejs/biome migrate eslint --write --include-inspiredOptions
| Flag | What it does |
|---|---|
| --write | Write the migrated config to biome.json |
| --include-inspired | Map rules Biome marks as inspired by an ESLint rule |
| --include-nursery | Also map to nursery (unstable) rules |
In CI
Run migrate locally, commit the resulting biome.json, and review the diff. Do not run migrate in the verification pipeline; the pipeline should run biome ci against the committed config. Not every ESLint rule has a Biome equivalent, so expect some manual cleanup.
Common errors in CI
"Cannot find the ESLint configuration" means no supported config was discovered; ensure an .eslintrc or eslint.config file is present. Plugin rules with no Biome counterpart are skipped and noted. After migrating, biome ci may surface new diagnostics because Biome defaults differ from your old ESLint setup.