Is there a good reason why `.babelrc` at the top directory is not a default way to customize `babel-loader` config?

I mean, that’s probably something that would be expected by many, wouldn’t it? Especially considering that react-app-rewire-eslint enables .eslintrc support. Well, at least that’s something I was confused about initially myself

The only related thing I found is #83 but that’s more about Jest config. And it just seems weird to have it partially supported in some places but not the others and having to duplicate the same configuration options in two different places

What I’d like to propose is adding another function to the main package that would simillarly to injectBabelPlugin locate rules using babel-loader and switch babelrc option to true.
This way it will be both, explicit and backwards compatible

[unconfident]

Just don’t and have everything you need in .babelrc like everyone else?

update: But I get your point. That said, if babelrc: true were to become a default in 2.0 I would prefer to not have babel-preset-react-app included in this “obscure” way and just have it specified in .babelrc instead with minimalistic loader configuration

[unconfident]

This will behave slightly weird and possibly differently for CRA and Jest if you do it like this. Please see “protip” part of my comment from two weeks ago

tl;dr: you want to replace whole options object instead of modifying it