-
Notifications
You must be signed in to change notification settings - Fork 49.6k
Closed
Labels
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
Description
What kind of issue is this?
- React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- react-compiler-healthcheck (build issue installing or using the healthcheck script)
Link to repro
Repro steps
useSyncState
and useEditable
break when the React Compiler runs on it. So I added 'use no memo'
to the top of useSyncState
and useEditable
. In both these places, eslint-plugin-react-compiler
reports that the 'use no memo'
directive is unused. Even though this directive is the only difference between a passing E2E test and a failing one!

- Related to [Compiler Bug]: Compiler doesn't catch ref access in render #31406, where I report that the compiler should ideally bail out on these hooks so the
'use no memo'
directive becomes unnecessary.
How often does this bug happen?
Every time
What version of React are you using?
18.3.1
What version of React Compiler are you using?
19.0.0-beta-6fc168f-20241025
lukpsaxo, ahkhanjani, Jorn08, ddolcimascolo, valtism and 18 more
Metadata
Metadata
Assignees
Labels
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