Custom configuration

As mentioned in #2758 and in #3878, we could need a file in which we store our conf, such as the vendors, or the externals (to support cdn), or even custom babel config (ahahah)

Why not a cra field in the package.json and a .crarc / .crarc.json and a .crarc.js files that contains our custom config ?

[mudrz]

To expand with some additional feedback:

• Angular (2-6) has a pretty decent configuration model (.angular-cli.json) and cli to customise the initial model
• Vue has taken this to an even higher level with interactive cli (source: https://vuejsdevelopers.com/2018/03/26/vue-cli-3/) and in addition to that there will even be UI (source: https://twitter.com/Akryum/status/981541152620011521)

The approach taken by create-react-app was a step in the right direction at the time it was released, but now it feels stale.

It seems that the project does not have the same amount of support from Facebook as the other projects have received from their respective companies/sponsors.

Is there anything we as a community can do to get better 1st party support for this project and its future? Is it even feasible to expect create-react-app to be expanded to accommodate real-world scenarios that the React community faces?

I realize that one can eject (I do) or use 3rd party projects, but having a mature first party solution that sets some less opinionated style guidelines and project structure propagates in EVERY library and project the community creates. Which in turn creates higher quality and easier to navigate OS libraries.

Any feedback on what we can expect and what we cannot expect would be highly appreciated. And thank you for all the great work so far, this project truly made a big difference 👍.

[danielkcz]

I do really like the mission of CRA, it makes the entrance to React world much easier. However, I am more inclined to allow at least some optional configuration that is most commonly requested (eg. custom webpack loaders, babel plugins…) with a big red warning that doing that means jumping into a rabbit hole.

For example, as I’ve mentioned in a linked issue, it’s really great that .graphql is now recognized, but if I prefer to use .gql I have to either eject or pollute NPM with my own fork of react-scripts for this tiny little change.

Just my two cents, I can understand it’s not as easy as it seems to allow such level of customization.