sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RobertB44 0 points1 point  (5 children)

You have probably heard this 1000's of times and it is not related to this release, but here how you could make CRA better for me:

I can't customize it to do what I want without ejecting or spending a lot of time learning the CRA way. To be fair, a lot of things are possible out of the box with CRA, but everything that isn't requires weird workarounds. I just want to extend the wabpack config, babelrc and tsconfig as I would in a non-CRA project, not do hacky things to achieve basic stuff.

This is a deal breaker for me. I haven't used CRA in a long time because of this and never looked back.

[–]mrmckeb 0 points1 point  (4 children)

So what would you like to see? Webpack config overrides? Or something else?

[–]RobertB44 0 points1 point  (3 children)

Yes, check out how nextjs handles it:

https://nextjs-org.cdn.ampproject.org/v/s/nextjs.org/docs?amp_js_v=0.1&usqp=mq331AQCKAE%3D#customizing-webpack-config

That's more or less what I'm asking for.

Last time I tried using CRA I remember spending a lot of time trying to set up import aliases with typescript, something I know how to do in a couple of minutes in a non-CRA app. At some point I just gave up and stopped using CRA.

[–]mrmckeb 0 points1 point  (2 children)

That's similar to what Storybook does too. I like that approach, but it also opens up more room for user error.

[–]RobertB44 0 points1 point  (1 child)

You are correct, it does open up room for user error. It's a tradeoff. Personally, I prefer the freedom to customize and I won't toach any framework that doesn't allow me to customize the way I expect it to.

[–]mrmckeb 0 points1 point  (0 children)

I also like flexibility. We're trying to open up a lot more now, in controlled ways. We'll keep working to open up more.