Skip to content

docs: add a link to the Oxlint rule for component exports alongside the ESLint rule link.#1141

Merged
sapphi-red merged 1 commit intovitejs:mainfrom
connorshea:main
Mar 12, 2026
Merged

docs: add a link to the Oxlint rule for component exports alongside the ESLint rule link.#1141
sapphi-red merged 1 commit intovitejs:mainfrom
connorshea:main

Conversation

@connorshea
Copy link
Contributor

Description

The rule from eslint-plugin-react-refresh - for only exporting components - is also available as a ported Rust rule in Oxlint, and I figure it makes sense to link it in the docs for users of Oxlint.

Also fixes the capitalization for ESLint :)

…he ESLint rule link.

Also fix the capitalization for ESLint :)
@connorshea connorshea changed the title docs: Add a link to the Oxlint rule for component exports alongside the ESLint rule link. docs: add a link to the Oxlint rule for component exports alongside the ESLint rule link. Mar 12, 2026
@ArnaudBarre
Copy link
Member

BTW I did a bit rewrite of the rule in 0.5 to catch more issues and have less false positive. I don't know if this kind of think is tracked on oxlint side. One day I will take time to finish migrating from ESLint of oxlint, so I might do it myself one day 😄

@sapphi-red sapphi-red merged commit 3a17886 into vitejs:main Mar 12, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants