Doist / Doist/react-compiler-tracker
Support additional ways the React Compiler can be configured
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 11
Description
Currently, the tracker merges any Babel config files it finds in the consuming project with its own base config. However, this is not a true representation of how the consuming project is using the compiler. For example, Twist is using Vite, where its own exclusion list is defined in vite.config.ts.
We currently get around that by asking consumers to define their own inclusion list in .react-compiler-tracker.config.json using a single glob pattern, but it is limited (no multiple glob pattern support) and requires duplication.
Here are all the ways the compiler can receive its configurations from Babel through different build tools: https://react.dev/learn/react-compiler/installation
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 reviewing the current .react-compiler-tracker.config.json approach, the consuming project's vite.config.ts, and the compiler configuration methods listed in the React installation guide. Done means the tracker can represent supported build-tool configuration methods without requiring duplicated inclusion settings, including multiple glob patterns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, react, typescript, vite
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100