feat(preferred): Add oxlint as an alternative for eslint-plugin-import and eslint-plugin-react#664
Open
connorshea wants to merge 8 commits into
Open
feat(preferred): Add oxlint as an alternative for eslint-plugin-import and eslint-plugin-react#664connorshea wants to merge 8 commits into
oxlint as an alternative for eslint-plugin-import and eslint-plugin-react#664connorshea wants to merge 8 commits into
Conversation
… eslint-plugin-react. I added the disclaimer about Oxlint not being a full drop-in replacement (though it's a bit repetitive since the disclaimer is basically mentioned twice in each of these pages) to match the disclaimer on `eslint-plugin-react` about the `@eslint-react/eslint-plugin` package.
…ort` and `eslint-plugin-react`.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
ghostdevv
requested changes
May 20, 2026
Co-authored-by: Willow (GHOST) <ghostdevbusiness@gmail.com>
ghostdevv
approved these changes
May 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Resolves #663.
📚 Description
Suggest Oxlint as an alternative to these two plugins, as both plugins' rules are supported natively (though only a large majority of the rules, not all of the rules).
I added the disclaimer about Oxlint not being a full drop-in replacement to match the disclaimer on the
eslint-plugin-reactpage about the@eslint-react/eslint-pluginpackage. The disclaimer is a bit repetitive since it's basically mentioned twice in each of these pages (again, to match how the@eslint-react/eslint-pluginpackage section was written), I can simplify it to just the NOTE section if preferred.I've also added
oxlintin the preferred JSON file for these two packages. I can add this toeslint-plugin-vitestas well, but it feels like a different kind of replacement given that the current entry is only technically about a package rename (eslint-plugin-vitestto@vitest/eslint-plugin). I think it's not a good idea to add for eslint-plugin-node right now, as only a small portion of the rules from that plugin have been ported to Oxlint so far.eslint-plugin-importcurrently has 123 total deps and subdeps. So I think it's definitely worth suggesting alternatives.You can see the Oxlint rules list here: https://oxc.rs/docs/guide/usage/linter/rules.html
And issues for tracking the rule porting process on each plugin here: oxc-project/oxc#481