3 ms·

Am I the only one here that loves the idea of create-react-app but doesnt use it because it is almost impossible (or rather, was almost impossible as of a few m

Am I the only one here that loves the idea of create-react-app but doesnt use it because it is almost impossible (or rather, was almost impossible as of a few months ago) to utilize features in webpack etc. The whole idea of "you need to eject" and can only eject one time to install a package that allowed me to use JSX If/Else statements [1] turned me off to the whole thing. Now I have a custom project and just create new ones with cookiecutter Im open to being wrong here, but the experience kinda sucked IMO. [1]https://github.com/AlexGilleran/jsx-control-statements https://github.com/AlexGilleran/jsx-control-statements

pcmaffey 7y ago
Use craco. https://github.com/gsoft-inc/craco https://github.com/gsoft-inc/craco I needed it to get CRA working in a lerna/yarn workspaces monorepo. Super impressed with how easy config is.
- misiti3780 7y ago
  this is exactly what i was looking for, thank you!
zuck9 7y ago
You can use https://github.com/timarney/react-app-rewired https://github.com/timarney/react-app-rewired to override anything in the default CRA config
- sli 7y ago
  I don't think this works on CRA 3 and it's development has slowed a lot. craco (listed in the alternatives) supports CRA 3.
  - zuck9 7y ago
    I've been using it for a while with CRA 3 / react-scripts 3.2 Works fine for overriding Webpack config at least.
w33ble 7y ago
Nope. My company ended moving off it because it’s not extensible at all. create-poi-react-app is a nice alternative, same functionality (and more) while using webpack chaining and allowing you to bring your own eslint config (or anything else).
JMTQp8lwXL 7y ago
I see comments praising they can now use new ECMAScript proposals, e.g., nullish coalescing. If you hadn't been at the mercy of an abstracted build tool, you could've upgraded your build system yourself. I don't like the idea of running my projects like that. If I want something in my project, I get it. There's none of this "waiting around" for it.
ng12 7y ago
Yeah, it's such a huge failure on Facebook's part. It's completely unusable in an enterprise environment and I can only recommend it for small one-off applications. The tagline they use but is "convention over configuration" but it's really "convention without configuration". It's frustrating the amount of times you find a GitHub issue for a feature you're looking for and the answer from the CRA team is "well we've decided you don't really need it" -- even for things that are a simple one or two line config in Webpack.

pcmaffey 7y ago

Use craco. https://github.com/gsoft-inc/craco https://github.com/gsoft-inc/craco I needed it to get CRA working in a lerna/yarn workspaces monorepo. Super impressed with how easy config is.

misiti3780 7y ago
this is exactly what i was looking for, thank you!

zuck9 7y ago

You can use https://github.com/timarney/react-app-rewired https://github.com/timarney/react-app-rewired to override anything in the default CRA config

sli 7y ago
I don't think this works on CRA 3 and it's development has slowed a lot. craco (listed in the alternatives) supports CRA 3.
- zuck9 7y ago
  I've been using it for a while with CRA 3 / react-scripts 3.2 Works fine for overriding Webpack config at least.

w33ble 7y ago

Nope. My company ended moving off it because it’s not extensible at all. create-poi-react-app is a nice alternative, same functionality (and more) while using webpack chaining and allowing you to bring your own eslint config (or anything else).

JMTQp8lwXL 7y ago

I see comments praising they can now use new ECMAScript proposals, e.g., nullish coalescing. If you hadn't been at the mercy of an abstracted build tool, you could've upgraded your build system yourself. I don't like the idea of running my projects like that. If I want something in my project, I get it. There's none of this "waiting around" for it.

ng12 7y ago

Yeah, it's such a huge failure on Facebook's part. It's completely unusable in an enterprise environment and I can only recommend it for small one-off applications. The tagline they use but is "convention over configuration" but it's really "convention without configuration". It's frustrating the amount of times you find a GitHub issue for a feature you're looking for and the answer from the CRA team is "well we've decided you don't really need it" -- even for things that are a simple one or two line config in Webpack.