4 ms·
I've been finding that I go outside the base config quite quickly. I wanted to compile a second app with different babel settings and have that in my webpack c
by awongh 7y ago
I've been finding that I go outside the base config quite quickly.
I wanted to compile a second app with different babel settings and have that in my webpack config.
I gave up on it after a few hours of trying to figure out what I would need.
Is this really a super rare case that only experts should attempt?
When I ejected CRA it gave me a 600 line config file.
I think I also find the general attitude of the community ("it's all modular!") to be disingenuous. Just bundle all this stuff into a monoremp massive npm package and be done with it, ala rails.
- chrisweekly 7y agoI think CRA does an amazingly good job for the standard non-ejected scenario. Ejecting and hacking on the output is educational, but rarely a good idea. Which is fine. My chief complaint is the lack of robust, non-ejection extensibility. Projects like CRACO, and babel macros, IMHO should be standard and officially supported.
- nicoburns 7y ago> When I ejected CRA it gave me a 600 line config file. This is one of my least favourite thing about CRA. The equivalent Webpack config tailored to the needs of my project is generally only 100-200 lines long. CRA makes things far more complicated than it needs to be because it has to support everyone's requirements.
- jakelazaroff 7y agoOut of curiosity, what do you end up needing that's not supported by default by CRA (or Next or Gatsby)? I've started a bunch of apps with CRA, and not once have I needed anything that's not already there.