-
Notifications
You must be signed in to change notification settings - Fork 50.6k
Open
Labels
Status: 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-hooks (build issue installing or using the eslint plugin)
- react-compiler-healthcheck (build issue installing or using the healthcheck script)
Link to repro
N/A — feature request.
Repro steps
Healthcheck only prints "Successfully compiled X out of Y components" and does not show which components failed.
Proposal: Add a --verbose flag to print for each failed component:
- file path
- location (line/column when available)
- error reason
The data is already collected in ActionableFailures / OtherFailures in reactCompiler.ts; it only needs to be printed when the flag is set. That would make it possible to fix remaining violations and to trust the reported counts.
Related: #29078 (closed), #29677 (open — "how do I find the remaining components?").
How often does this bug happen?
Every time
What version of React are you using?
19.2.4
What version of React Compiler are you using?
babel-plugin-react-compiler@1.0.0 (via Expo SDK 54); react-compiler-healthcheck@19.1.0-rc.3
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Status: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug