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.
11
+
**ESLint React** addresses critical gaps in the existing `eslint-plugin-react`for modern React ecosystems. Despite React's core being renderer-agnostic, the current plugin maintains DOM-specific assumptions that conflict with alternative renderers like React Native and React Three Fiber. This can sometimes cause confusion and problems.
12
12
13
-
Although you can use it with other renderers, it will always assume that you are using the React DOM, even if you are working with a codebase that uses a different renderer. This can sometimes cause confusion and problems[³].
13
+
**ESLint React** is designed to be renderer-agnostic. It offers:
14
14
15
-
Unfortunately, the maintainers of `eslint-plugin-react` refuse to change that[⁴].
15
+
- Composable and extensible rulesets
16
+
- Context-aware checks adapting to different environments
17
+
- Unified code standards regardless of render target
16
18
17
-
Just as in [Beyond the DOM](https://legacy.reactjs.org/docs/design-principles.html#beyond-the-dom) we believe the future of React Linter is not limited to the DOM. This influences every decision made in ESLint React, and it is the reason why we created it.
19
+
This approach ensures consistent code quality standards and reliable linting experience across all React platforms, including React DOM, React Native, React Three Fiber, and more.
18
20
19
21
</Accordion>
20
22
@@ -73,8 +75,3 @@ To smoothly transition, we suggest reviewing the rules in ESLint React and runni
0 commit comments