-
Notifications
You must be signed in to change notification settings - Fork 50.9k
fix: potential null dereference in react compiler configuration (#32571) #36163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,5 +15,5 @@ | |
| const baseConfig = require('./babel.config-ts'); | ||
|
|
||
| module.exports = { | ||
| plugins: baseConfig.plugins, | ||
| plugins: Array.isArray(baseConfig.plugins) ? baseConfig.plugins : [], | ||
|
||
| }; | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fallback will silently drop plugins if
baseConfig.pluginsis anything other than an array (e.g. a function/object due to a future change), which could lead to the compiler artifact being transformed incorrectly while tests still run. Consider only defaulting fornull/undefinedand throwing a clear error for other unexpected types so misconfiguration fails fast with a helpful message.