[internal] Adopt react compiler?
Open
Nobody has claimed this yet.
discussion
internal
performance
scope: all components
scope: code-infra
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary
Same as https://github.com/mui/base-ui/issues/809.
The action plan would involve:
- Close #42548
- Run all the tests on the output of the compiler. I believe we already do this with the Babel optimizations that we have, so won't be too hard. It's important to guarantee behavior.
- Publish the source with the output of the compiler
Motivation
Performance.
Now, to be fair, we likely want to invest time into this for Base UI first, since in Material UI there should be barely anything to optimize (it should be almost only about style).
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 by reading the linked Base UI issue and the existing Babel optimizations, then determine how the React Compiler output would enter the current test and publishing flow. Run all tests against the compiler output; done means behavior is verified and the compiled source is published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript, react
- Domain
- build-system, frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100