Oxlint Beta

[Boshen]

@DonIsaac and I had a meeting and agreed to introduce the following features for a Oxlint Beta release. This feature list is minimal due to our lack of time and resources.

1. ESLint V8 cascading configuration - linter: nested file configuration #7408
2. "overrides"
3. display unsupported rules
4. enable plugins from the plugins array

Note ESLint V9 flat config is out of scope.

[DonIsaac]

note: refactor to split serde-able eslintrc struct from the actual config used by the linter is in progress. Once complete, we can start adding fields to the config file.

[AndreaPontrandolfo]

Reading the features list, everything you listed are .eslintrc mechanics, that are not present in ESLint V9 FlatConfig, because it works completely differently.
So my understanding is that you are gonna do a TON of work to support a legacy configuration system (soon to be deprecated) and right after you would have to scrap all of that to migrate to V9 support.
Why is that?

[DonIsaac]

@Boshen we need to push back the due date on this milestone. I won't have this complete before my presentation at SquiggleConf.

[Boshen]

@Boshen we need to push back the due date on this milestone. I won't have this complete before my presentation at SquiggleConf.

No pressure! It was a hypothetical date anyway.

[Boshen]

Shall the next release aim for completing this?

[Boshen]

Final issue for beta: #7408

[nrayburn-tech]

Once the nested configs are supported it might make sense to make sure the IDE plugins are updated and contain all the desired features before doing a beta blog post. VS Code gets a lot of attention, but the other two plugins don’t get too much attention right now.

I have been waiting for the changes in VS Code to settle some before syncing up the JetBrains plugin.
I’m not sure about the vim (neovim?) plugin. It looks very similar to the VS Code plugin so it may not be too hard to update, but I don’t have any experience with it.