Those instructions have us install npm install react-compiler-runtime@latest and then you have to pass a target flag to React Compiler. How do we do that within Next.js? It looks like from Next's React Compiler's docs we don't manually set up the babel-plugin-react-compiler manually, I'm guessing ... More on github.com

One ever present debate in the React community had been whether you should `useMemo`/`useCallback` all non-primitive props or not. I've often taken the position that you should in real world teams because it's too much work to determine exactly when to otherwise , whereas others argue that it's too much runtime overhead (and noise) and not worth it. u/acemarke has a good summary of the arguments . All that to say, I was curious if this compiler is essentially the React team conceding that you _should_ memoize everything. The answer is pretty interesting - the compiler actually memoizes things in a more efficient way than `useMemo` can . So it's almost the best of all worlds: improved rendering performance from memoization, cheaper memoization cost, and none of the noise of `useMemo`s sprinkled everywhere. I think we'll have to wait a bit longer to see if this works out in practice, and I'm not crazy about having to add another layer of transpilation, but if it works well this will be a pretty big win for React projects in general I think. More on reddit.com

Still won't change one fundamental difference for me. In React, you write HTML in JavaScript. (This code gets in my way) In Svelte, you write JavaScript in HTML. (This code gets out of my way) More on reddit.com

The compiler introduces a bunch of new pitfalls - it’s now more important than ever to follow React’s rules of hooks , and to avoid reading or writing ref.current during a render . You should install the React Compiler ESLint Plugin today to learn about the obvious problems in your codebase that block compilation. But the linter can’t catch all the Undefined Behavior that the compiler can trigger in your code, and it will never be able to catch everything without solving the Halting Problem. I’ve been trying to enable the compiler for my company’s codebase. The compiler causes a bunch of E2E tests to fail, and there are no error messages or warnings explaining why the E2E tests are suddenly failing. It’s actually unfortunately quite similar to tracking down UB in C or C++ that was triggered by compiling with -O2 or the like. The compiler succeeds, and the code runs without crashing. But the E2E test expects renders and refreshes that are no longer happening, all because we broke one of React’s rules somewhere in our stack. The only way I’ve made progress has been through binary search: my function sources(filename) in my ReactCompilerConfig hashes the filename into an integer, then uses the bits in the integer to determine if the file should be compiled. Then we iterate and recurse based on whether the E2E test succeeds or fails. This lets us find a minimal set of files for which compilation will break the test, making it easier to track the source of UB down. More on reddit.com