Replies: 1 comment 2 replies
-
An earlier version of the ESLint migrator displayed the rules that were not migrated. However, this was too much noise for the user, I decided to remove it. However, you made a good point. We could perhaps support something similar to the linter/formatter reporters: ❯ biome migrate eslint --reporter=json
{
// format to define
} The reporter could output the migrated rules and the non-migrated rules. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Would it be possible to have ESLint migrator output which rules it could not migrate?
I did an experimental migration of neostandard: neostandard/neostandard#77 But without me doing some manual diffs and math I can't tell how much of the neostandard config that the migration covers – whether it is a 40% subset, a 80% subset and which rules (maybe some vital ones) that couldn't be migrated.
If one could even get the migrator to output this in JSON or similar (eg. using a
--json
flag) then I could probably write up a GitHub Action that continuously generates an up to date Biome config for every new change in neostandard.Beta Was this translation helpful? Give feedback.
All reactions