Re:Lessons learned as a React contractor
by krrishd on Thursday January 05, 2017 @06:16PM
(#13332398)
just curious, why is ejecting from create-react-app bad? some of the symlinking stuff involved with create-react-app feels unnecessary but I still value the amount of boilerplate it takes out
[ Parent
| on HN ]
Re:Lessons learned as a React contractor
by hoodoof on Thursday January 05, 2017 @07:53PM
(#13332960)
The point of create-reaact-app is that your build process is zero configuration.
The deepest pain point of JavaScript development is undoubtedly build configuration i.e. webpack and babel.
If you stick with create-react-app then you manage to remain in a zero build config world, which is a happy world to live in.
Re:Lessons learned as a React contractor
by tomduncalf on Friday January 06, 2017 @04:34AM
(#13334985)
> The deepest pain point of JavaScript development is undoubtedly build configuration i.e. webpack and babel.
Really? Perhaps I've been doing this too long, but once you get your head round the basics I really don't think it's that bad
Re:Lessons learned as a React contractor
by ccallebs on Friday January 06, 2017 @08:44AM
(#13336125)
Is there a resource you can recommend to get your head around all the basics?
Re:Lessons learned as a React contractor
by acemarke on Friday January 06, 2017 @11:31AM
(#13337609)
The new Webpack docs are great ([0]). Also, my React/Redux links list ([1]) has a couple sections on Webpack tutorials ([2]) and Webpack advanced techniques ([3]) like Hot Module Reloading, file chunking, and build optimization.
[1] https://github.com/markerikson/react-redux-links
[2] https://github.com/markerikson/react-redux-links/blob/master...
[3] https://github.com/markerikson/react-redux-links/blob/master...
Re:Lessons learned as a React contractor
by krrishd on Thursday January 05, 2017 @08:00PM
(#13333019)
Right, but even upon ejecting I still retain the ability to build/start/test with one command, the only difference is that the build/start/test scripts become static
Re:Lessons learned as a React contractor
by acemarke on Thursday January 05, 2017 @06:33PM
(#13332507)
Mostly because you can get the benefit of improvements to the build config just by updating the one `react-scripts` dependency. For example, 0.8 enabled proper sourcemaps support in Webpack (and 0.8.2 bumped the Webpack dependency to fix a problem with not being able to set breakpoints in sourcemapped code). If you eject, you don't get those easy updates, as the config files are now a permanent part of your own project.
Re:Lessons learned as a React contractor
by jowiar on Thursday January 05, 2017 @07:13PM
(#13332743)
There are a couple dealbreakers for now, but I'm seriously looking forward to the day I can migrate our stack ON to create-react-app largely for this reason. Having other people working to make my dev experience better is a huge plus.
Re:Lessons learned as a React contractor
by chrisweekly on Friday January 06, 2017 @12:19AM
(#13334160)
Next.js (built on top of React and Redux, by the ppl who brought us socket.io) is a zero-config option that looks way better to me than CRA.