Don't Eject Your Create React App

#1

Post by level » Thu, Jan 17, 2019, 4:39 PM UTC

Don't Eject Your Create React App
medium.com

Re: Don't Eject Your Create React App

#2

Post by ardfie » Thu, Jan 17, 2019, 5:12 PM UTC

What I got when I followed the link

http://imgur.com/3gcROaQ

Medium is shockingly bad. I see absolutely no value in this service any more.

Re: Don't Eject Your Create React App

#3

Post by wilkystyle » Thu, Jan 17, 2019, 5:16 PM UTC

ardfie wrote: post #2

What I got when I followed the link http://imgur.com/3gcROaQ Medium is shockingly bad. I see absolutely no value in this service any more.

I have reader mode permanently enabled for medium.com for Safari on iOS, and on Chrome for MacOS I have Ublock Origin rules to heavily filter out elements on the page.

Re: Don't Eject Your Create React App

#4

Post by hyfgfh » Thu, Jan 17, 2019, 5:26 PM UTC

Don't even use create react app

Re: Don't Eject Your Create React App

#5

Post by ng12 » Thu, Jan 17, 2019, 5:48 PM UTC

I just wish CRA would give me a hook to touch the webpack configs. I'm willing to bite the pain of needing to rewrite my custom configs if they move to something else.

Simple example: with webpack it's trivial to configure it to load env-specific extensions. You can have foo.js, foo.dev.js, and foo.mock.js and it will import the correct one automatically based on an env variable. It's three lines of code that I use in all my React projects and it's honestly enough to keep me away from CRA.

Re: Don't Eject Your Create React App

#6

Post by ojhughes » Thu, Jan 17, 2019, 5:50 PM UTC

It really blows my mind that the latest, greatest technology is so difficult to work with it requires a meta-tool manage the process.

Re: Don't Eject Your Create React App

#7

Post by level » Thu, Jan 17, 2019, 5:52 PM UTC

ng12 wrote: post #5

I just wish CRA would give me a hook to touch the webpack configs. I'm willing to bite the pain of needing to rewrite my custom configs if they move to something else. Simple example: with webpack it's trivial to configure it to load env-specific extensions. You can have foo.js, foo.dev.js, and foo.mock.js and it will import the correct one automatically based on an env variable. It's three lines of code that I use i…

The article covers the use-case of making small modifications to the build. react-app-rewired[1] and customize-cra[2] give you access to tweak the webpack build indirectly. While babel-macros[3] in CRA 2.X give you access to the babel transpilation step without having to eject. While it's not exactly what you're referring to, it does get you a little bit closer to the build.

[1] https://github.com/timarney/react-app-rewired/

[2] https://github.com/arackaf/customize-cra

[3] https://babeljs.io/blog/2017/09/11/zero-config-with-babel-ma...

Re: Don't Eject Your Create React App

#8

Post by JustinBrown » Thu, Jan 17, 2019, 5:54 PM UTC

Agreed. It's becoming harder and harder to justify managing your own React pipeline, even in the rare cases where something might be missing that I want included.

Re: Don't Eject Your Create React App

#9

Post by ng12 » Thu, Jan 17, 2019, 6:11 PM UTC

ojhughes wrote: post #6

It really blows my mind that the latest, greatest technology is so difficult to work with it requires a meta-tool manage the process.

CRA actually has almost nothing to do with React and a whole lot to do with other tools (Babel, ES6, Webpack, Jest). You don't need most of them to build a React application, it's mostly about developer experience and the surrounding ecosystem.

FWIW Angular does the same thing with Angular-CLI. The "problem" is the web dev ecosystem, not React itself.

Re: Don't Eject Your Create React App

#10

Post by tbirrell » Thu, Jan 17, 2019, 6:53 PM UTC

Can someone explain what ejection is? I'm not familiar with this terminology. How is it different from say, editing your package.json or webpack.mix.js files?