React
react.dev › blog › 2025 › 10 › 07 › react-compiler-1
React Compiler v1.0 – React
React Compiler includes an ESLint rule that helps identify code that breaks the Rules of React. The linter does not require the compiler to be installed, so there’s no risk in upgrading eslint-plugin-react-hooks.
GitHub
github.com › reactwg › react-compiler › discussions › 25
How do I use eslint-plugin-react-compiler with eslint 9? · reactwg/react-compiler · Discussion #25
import reactCompilerPlugin from 'eslint-plugin-react-compiler'; export default [ { plugins: { "react-compiler": reactCompilerPlugin }, rules: { "react-compiler/react-compiler": "error", }, files: ["**/*.res.mjs"] }];
Author reactwg
React Compiler and exhaustive-deps
Your last paragraph is correct, it should be possible to rewrite your useEffect to do what you want without breaking the rule. Share some code if you can. Disabling the lint rule globally is a recipe for disaster as the compiler will assume the rule is enforced even though it isn’t, so everything downstream from that will possibly be corrupted. More on reddit.com
2
7
June 4, 2024eslint-plugin-react-no-manual-memo: ESLint plugin for React Compiler users to flag any usage of useMemo, useCallback, and React.memo
Haha nice, that's a clever approach to adapting to React Compiler More on reddit.com
2
24
October 5, 2025[eslint-plugin-react-compiler] eslint-plugin-react-compiler is not compatible with eslint 9 (Flat config)
Summary I'm trying to use version 19.0.0-beta-6fc168f-20241025, we already use compiler in production, but we still can't use eslint plugin because it's not compatible with flat config More on github.com
4
August 16, 2024React Compiler Setup [Experimental] - Experimental Features - RedwoodJS Community
Try it out You can now try this ... & serve. If you inspect your pages with the react dev tools you should hopefully see where the compiler has performed auto memoisation. This command will install both the eslint and babel plugin packages. It will also enable a flag in your ... More on community.redwoodjs.com
1
1
May 15, 2024Videos
ESLint Configuration • React JS Programming • React ...
09:33
22. Install ESLint in the React Project and configure React Plugin ...
05:27
React Compiler / React Forget - with Vite - YouTube
03:03
What Is ESLint Used For In React? - Next LVL Programming - YouTube
09:59
React Setup - 05 - ESLint & Prettier - YouTube
02:25
ERROR in [eslint] Plugin "react" was conflicted between "package.json ...
Yarn
classic.yarnpkg.com › en › package › eslint-plugin-react-compiler
eslint-plugin-react-compiler
Fast, reliable, and secure dependency management
Reddit
reddit.com › r/reactjs › react compiler and exhaustive-deps
r/reactjs on Reddit: React Compiler and exhaustive-deps
June 4, 2024 -
Hey, guys! I’ve been testing the React Compiler Eslint plugin to see if my codebase could benefit from any changes ahead of React 19 stable. One problem that I’ve run into is that disabling exhaustive-deps inline throws an eslint error because I’m disabling a react eslint rule, implying that the component will be skipped for compiler optimization. However, if I disable the rule globally in my eslintrc, no error is thrown. This might just be a limitation of the linter.
My question is, if I disable this rule globally, will react compiler still refuse to optimize the components that don’t follow the rules of exhaustive-deps? Exhaustive-deps is a rule that I don’t think has historically been the best option, because there are cases when you want to only run a useEffect on mount, and not if the states inside them change. Or, sometimes you only want useEffect to run when some states change, but not when others change.
It could also be the case that I just don’t understand how to write good useEffects after 5 years of using them, so I’m open to feedback about other ways of achieving the goals outlined above in an elegant way.
Top answer 1 of 2
9
Your last paragraph is correct, it should be possible to rewrite your useEffect to do what you want without breaking the rule. Share some code if you can. Disabling the lint rule globally is a recipe for disaster as the compiler will assume the rule is enforced even though it isn’t, so everything downstream from that will possibly be corrupted.
2 of 2
7
If you are writing useEffects with dependencies that you don't want to trigger a new effect on change, then that's the problem you need to fix. You shouldn't have to do that
Expo Documentation
docs.expo.dev › development process › reference › react compiler
React Compiler - Expo Documentation
November 3, 2025 - Run npx expo lint to ensure ESLint is setup in your app, then install the ESLint plugin for React Compiler:
npm
npmjs.com › package › eslint-plugin-react-hooks
eslint-plugin-react-hooks - npm
The official ESLint plugin for React which enforces the Rules of React and other best practices.
» npm install eslint-plugin-react-hooks
Published Oct 24, 2025
Version 7.0.1
Repository https://github.com/facebook/react
Homepage https://react.dev/
LogRocket
blog.logrocket.com › home › react compiler rc: what it means for react devs
React Compiler RC: What it means for React devs - LogRocket Blog
May 2, 2025 - As mentioned before, the compiler relies on strict adherence to React’s rules. That’s what the dedicated compiler plugin helped enforce. With RC, you no longer need that separate package. It’s now part of the main ESLint plugin for React.
React
react.dev › learn › react-compiler › installation
Installation – React
This is safe: the compiler will continue optimizing other parts of your codebase. You don’t need to fix all violations immediately. Address them at your own pace to gradually increase the number of optimized components. ... If you haven’t already configured eslint-plugin-react-hooks, follow the installation instructions in the readme.
React
react.dev › reference › eslint-plugin-react-hooks
eslint-plugin-react-hooks – React
This plugin helps you catch violations of React’s rules at build time, ensuring your components and hooks follow React’s rules for correctness and performance. The lints cover both fundamental React patterns (exhaustive-deps and rules-of-hooks) and issues flagged by React Compiler. React Compiler diagnostics are automatically surfaced by this ESLint plugin, and can be used even if your app hasn’t adopted the compiler yet.
Reddit
reddit.com › r/reactjs › eslint-plugin-react-no-manual-memo: eslint plugin for react compiler users to flag any usage of usememo, usecallback, and react.memo
r/reactjs on Reddit: eslint-plugin-react-no-manual-memo: ESLint plugin for React Compiler users to flag any usage of useMemo, useCallback, and React.memo
October 5, 2025 -
As someone who learned React in 2022, I write memoization hooks basically by instinct at this point, and I needed something to tell me to stop doing that now that React Compiler is here and tells us to not do that any more.
So, I wrote a little ESLint plugin to catch when I write useMemo, useCallback, or React.memo, and I figured I'd share it with everyone else too. Enjoy!
p.s. I made sure to include React Compiler Playground links in the docs so you can see React Compiler's memoization in action—not just blindly trust that the rules are right!
GitHub
github.com › facebook › react › issues › 31392
[eslint-plugin-react-compiler] eslint-plugin-react-compiler is not compatible with eslint 9 (Flat config) · Issue #31392 · facebook/react
August 16, 2024 - [eslint-plugin-react-compiler] eslint-plugin-react-compiler is not compatible with eslint 9 (Flat config)#31392
Author faradaytrs
LinkedIn
linkedin.com › posts › souravsadhukhan_reactjs-eslint-reactcompiler-activity-7384826987409903618-mvyx
eslint-plugin-react-hooks now catches React Compiler issues
We cannot provide a description for this page right now
Medium
jherr2020.medium.com › react-compiler-with-react-18-1e39f60ae71a
React Compiler With React 18
May 22, 2024 - First off, no, the React Compiler isn’t part of React 19. React 19 is just the React library. It doesn’t make any build changes for you. So to integrate the React Compiler means doing that work yourself. It also means that the React Compiler is optional.
Collected
collected.press › github › facebook › react@3a0ab8a7eea22394ba8948ff02af1c6d6e6e1921 › compiler › packages › eslint-plugin-react-compiler › README.md
eslint-plugin-react-compiler
ESLint plugin surfacing problematic React code found by the React compiler.
Medium
medium.com › @onix_react › introducing-react-compiler-1-0-3a15141ac6ae
Introducing React Compiler 1.0. The React team is thrilled to announce… | by Onix React | Medium
October 16, 2025 - This means developers no longer need to manually wrap values with useMemo, functions with useCallback, or components with React.memo. Instead, you can write idiomatic declarative code, and the compiler handles the performance heavy lifting, resulting in fewer re-renders and more responsive UIs. This release also features the integration of compiler-derived linting rules into the recommended presets of eslint-plugin-react-hooks.
RedwoodJS Community
community.redwoodjs.com › experimental features
React Compiler Setup [Experimental] - Experimental Features - RedwoodJS Community
May 15, 2024 - Try it out You can now try this ... & serve. If you inspect your pages with the react dev tools you should hopefully see where the compiler has performed auto memoisation. This command will install both the eslint and babel plugin packages. It will also enable a flag in your ...
Sanity
sanity.io › docs › help › react-compiler
React Compiler and Sanity | Sanity Docs
November 19, 2025 - In our experience it's incredibly rare for the compiler to create a regression, it typically choses to skip over optimizing components it deems unsafe, or too complex to safely memoize. Should a rare problem occur it's often enough to add 'use no memo' at the top of the affected file, to buy you time and find the fix. And then use ESLint with eslint-plugin-react-hooks to find issues that could be the root cause.
Nojaf
blog.nojaf.com › 2025 › 03 › 23 › rescript-eslint-and-the-react-compiler
ReScript, ESLint and the React Compiler | blog.nojaf.com
March 23, 2025 - import reactHooks from "eslint-plugin-react-hooks"; import reactCompiler from "eslint-plugin-react-compiler"; export default [ { files: ["src/*.res.mjs"], languageOptions: { ecmaVersion: "latest", sourceType: "module", }, plugins: { "react-hooks": reactHooks, "react-compiler": reactCompiler, }, rules: { "react-hooks/rules-of-hooks": "error", "react-hooks/exhaustive-deps": "warn", "react-compiler/react-compiler": "error", }, }, ];
GitHub
github.com › facebook › react › issues › 32575
[Compiler Bug]: eslint-plugin-react-compiler has incorrect type definitions · Issue #32575 · facebook/react
March 12, 2025 - Component: React CompilerStatus: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug ... eslint.config.js:11:3 - error TS2345: Argument of type '{ plugins: { 'react-compiler': { rules: { 'react-compiler': RuleModule; }; }; }; rules: { 'react-compiler/react-compiler': string; }; }' is not assignable to parameter of type 'InfiniteDepthConfigWithExtends'.
Author printfn
npm
npmjs.com › package › eslint-plugin-react-compiler › v › 0.0.0-experimental-16c1bb9-20241023
eslint-plugin-react-compiler - npm
October 23, 2024 - ESLint plugin to display errors found by the React compiler.. Latest version: 19.1.0-rc.2, last published: 7 months ago. Start using eslint-plugin-react-compiler in your project by running `npm i eslint-plugin-react-compiler`. There are 106 other projects in the npm registry using eslint-plugin-react-compiler.
» npm install eslint-plugin-react-compiler
Published May 14, 2025
Version 0.0.0-experimental-16c1bb9-20241023
Repository https://github.com/facebook/react