linter: automate generation of oxlint config

[Boshen]

Discussed in #4279

^{Originally posted by nicksrandall July 15, 2024}
It would be nice if there was a command (or docs) to create an up-to-date .oxlintrc.json file with all of the latest recommended rules. It's currently a pain to migrate from CLI to config file and maintain feature parity.

---

oxlint --init? https://biomejs.dev/guides/getting-started/#configuration

[nrayburn-tech]

In addition to a CLI command, might make sense to offer it as an IDE action/command. (I'm pretty sure the VS Code ESLint plugin has this as a command.)

[lachieh]

(This might not be the right place to discuss, but it seems related. I can create a new issue if preferred.)

It would be even better if there was a way to detect all of the rules from an existing eslint config file and generate a config from that. Biome has a migrate command that does this.

Unless I'm misunderstanding, the existing experience looks like this:

1. Install oxlint and eslint-plugin-oxlint
2. and/or:
   1. Enable either all rules, or just recommended rules in .oxlintrc.json
   2. Manually enable/disable rules from existing eslint config in .oxlintrc.json
3. run oxlint before eslint

I'd love to implement oxlint for the speed, but it's too time-prohibitive to migrate our existing config across to the oxlint config at the moment (step 2.2 above).