Same, but this is also why I feel burnt by create-react-app. There's so many important features the team has simply decided it won't support. One of the biggest issues with the React ecosystem is that there's nothing in between training wheels (CRA) and a motorcycle (rolling your own config). Maybe there's an opportunity for a new project there.
I also think that next.js might have some of what the gp is interested in
I have the same complaint, but this is definitely possible using e.g. react-app-rewired.
Adding custom webpack loader rules is as simple as replacing the calls to react-scripts with calls to react-app-rewired and adding a .js file with your customizations.
- https://github.com/gsoft-inc/craco
- https://github.com/harrysolovay/rescripts
- https://github.com/timarney/react-app-rewired
- https://github.com/arackaf/customize-cra
No, they're not "officially" supported, and you basically void the warranty by poking the configs manually, but the tools do what you want them to do.
AFAIK the "betweens" are Next.js, Blitz.js, Gatsby, Remix, Expo, etc.
Eventually I'll end up maintaining a company fork. It's more work for me but that's life. It's really just the dogmatic attitude of the CRA team that irks me.
Can't you switch Next.js to SSG for all routes since v9?
If enough people start using it, the original maintainers will see the need it covers, and hopefully will get rid of their dogmatic attitude, seeing how real people are adopting the approach they found no value in.
You avoid ejecting and benefit from upgrades to CRA, but you can customize anything you like.
There's a `customize-cra` lib that provides useful helpers that you can use to perform the most common operations.
90% of the reason I eject CRA. rewired is essential.