Unexpected Babel configuration behavior

The babel config override will override the loaderOptions, presets, and plugins for both of the babel-loader rules CRA has.

It seems like 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.

I would argue the behavior is unexpected since only files in src/ are supposed to get babel-preset-react-app and previously tools such as react-app-rewired only modified the first loader

[patricklafrance]

Hi @d3dc

This is indeed an easy fix if you want to customize what’s being configured for the files outside of the src/ directory.

I might wait before updating any code for this one since I don’t want to break anyone setup.

How could craco’s configuration be modified to accommodate your usecase?

Maybe an applyToExternalFiles boolean option with a default value of true ? Not sure though if it wouldn’t be more confusing than helping?

{
   babel: {
        presets: [],
        plugins: [],
        loaderOptions: { }
        applyToExternalFiles: true
   }
}

[patricklafrance]

Will be fix in #49