Skip to content

Support additional ways the React Compiler can be configured #105

@frankieyan

Description

@frankieyan

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions