You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a React component project as a common lib, i import the component lib into another React Web App, when i start the app ,many error were reported。
The babel config override the balel loaderOptions, presets, and plugins for both of the babel-loader rules CRA has.
the second loader shouldn't receive the presets and plugins by default, since the second loader is meant for:
#// Process any JS outside of the app with Babel.
// Unlike the application JS, we only compile the standard ES features.
babel config override of craco should be change, obviously, it is not rigorous and reasonable to merge plugins for each rule without distinguishing whether it is internal or external.
I have a React component project as a common lib, i import the component lib into another React Web App, when i start the app ,many error were reported。
The babel config override the balel loaderOptions, presets, and plugins for both of the babel-loader rules CRA has.
the second loader shouldn't receive the presets and plugins by default, since the second loader is meant for:
#// Process any JS outside of the app with Babel.
// Unlike the application JS, we only compile the standard ES features.
babel config override of craco should be change, obviously, it is not rigorous and reasonable to merge plugins for each rule without distinguishing whether it is internal or external.
this question similar to #36
this is one of the error info:
the app projects were used custum-cra, i'm migrating to craco, and this are their configurations:
craco.config.js
To reproduce
(list the steps to reproduce this behavior)
CRACO version
7.1.0
Additional information
bable plugins used to customName and customStyleName
The text was updated successfully, but these errors were encountered: