You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing `eslint-plugin-react` is a plugin for `react-dom` but named react[¹], it only supports React DOM[²] and does not being expected to be used with x-platform.
8
12
@@ -12,7 +16,9 @@ Unfortunately, the maintainers of `eslint-plugin-react` refuse to change that[
12
16
13
17
Just as in [Beyond the DOM](https://legacy.reactjs.org/docs/design-principles.html#beyond-the-dom) we believe that the community will benefit from a renderer-agnostic and x-platform-supported plugin. This is also the initial motivation for creating `eslint-react`.
14
18
15
-
## What is included in `eslint-react`?
19
+
</Accordion>
20
+
21
+
<Accordiontitle="What is included in eslint-react?">
16
22
17
23
Currently, it includes the following plugins:
18
24
@@ -25,12 +31,18 @@ Currently, it includes the following plugins:
25
31
26
32
You can view our long-term plans on the [roadmap](/roadmap#plugins-with-ecological-niche-explanation).
27
33
28
-
## Is there anything to note about migrating from `eslint-plugin-react` to `eslint-react`?
34
+
</Accordion>
35
+
36
+
<Accordiontitle="Is there anything to note about migrating from eslint-plugin-react to eslint-react?">
29
37
30
38
Please be aware that some rules may behave differently when transitioning to `eslint-react`. The rules in `eslint-react` are more closely aligned with the guidelines provided by [react.dev](https://react.dev). This alignment is due to `eslint-react` adopting [react.dev](https://react.dev) as its primary reference, rather than `eslint-plugin-react`.
31
39
32
40
To smoothly transition, we suggest reviewing the rules in `eslint-react` and running a comprehensive linting check on your codebase to identify and address any discrepancies introduced by the migration.
0 commit comments