[Compiler]: Detection for calling components as functions (instead of JSX)
Open
Nobody has claimed this yet.
Component: React Compiler
Type: Feature Request
- Dominant language
- JavaScript
- Stars
- 251k
- Forks
- 51.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
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
I am using conditional rendering ({status && MyItem}) in my JSX. When status is changed from false to true, the application crashes due to hooks not matching between renders. It works as expected without the compiler.
To reproduce, simply press the button in the example.
How often does this bug happen?
Every time
What version of React are you using?
18.2.0
What version of React Compiler are you using?
19.1.0-rc.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked React Playground reproduction and compare the behavior with and without the React Compiler enabled. Reproduce the crash by changing status from false to true, then trace the compiler's handling of conditional rendering with MyItem; done means the component renders without a hooks-mismatch crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- compilers, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100