about summary refs log tree commit diff
path: root/lib/react-compiler-runtime/index.js
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade React Compiler (take two) (#6460)dan2024-11-171-21/+0
| | | | | | | | | * Revert "Revert "React compiler beta and reenable rule (#5898)" (#6071)" This reverts commit 7111e38cd48c1c7e2b35ae978708fcb7a60a5dd7. * Update the compiler * Don't inline compiler runtime import
* Revert "React compiler beta and reenable rule (#5898)" (#6071)dan2024-11-011-0/+21
| | | This reverts commit 1fc684aaef6dd851b4d6c9a23673fcf4e7170722.
* React compiler beta and reenable rule (#5898)Samuel Newman2024-10-301-21/+0
| | | | | | | | | * use react compiler beta and reenable rule * use react-compiler-runtime * error -> warn * move runtime out of dev deps
* Add React Compiler (#4161)lauren2024-05-221-0/+21
* Install babel-plugin-react-compiler * Install eslint-plugin-react-compiler * Add and configure react-compiler-runtime React Compiler uses a small cache function from React 19 at runtime. Until it's possible to use R19 on RN, this adds a userspace implementation to polyfill the cache function * Add eslint-plugin-react-compiler to config * @lingui/macro should run as the first plugin @lingui recommends running their `macro` plugin [first in the pipeline](https://lingui.dev/ref/macro). Normally with the React Compiler, the compiler plugin should run first as we want to see the original code as it was written. However, this sometimes causes conflicts with other babel plugins. In this case, it looks like the @lingui/macro plugin does some very light transformation that the compiler can still understand and compile correctly, so let's run it first. Before this commit, the compiler would cause the @lingui/macro plugin to crash because it seems like it would strip off the `extra.raw` property off of StringLiterals which was being used [here](https://github.com/lingui/js-lingui/blob/1293412c5dcc565636403443788a5b5d4ca206c1/packages/macro/src/macroJsx.ts#L395). I need to figure out why the compiler is doing that but for now this works and should be a safe change unless there were specific reasons the macro plugin was placed 2nd to last.