4 ms·

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 amo

by krrishd 10y ago

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

acemarke 10y ago
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.
- jowiar 10y ago
  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.
  - chrisweekly 10y ago
    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.
hoodoof 10y ago
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.
- krrishd 10y ago
  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
- tomduncalf 10y ago
  > 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
  - ccallebs 10y ago
    Is there a resource you can recommend to get your head around all the basics?
    - acemarke 10y ago
      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. [0] https://webpack.js.org/ https://webpack.js.org/ [1] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links [2] https://github.com/markerikson/react-redux-links/blob/master/webpack-tutorials.md https://github.com/markerikson/react-redux-links/blob/master... [3] https://github.com/markerikson/react-redux-links/blob/master/webpack-advanced-techniques.md https://github.com/markerikson/react-redux-links/blob/master...

by krrishd 10y ago

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

acemarke 10y ago

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.

jowiar 10y ago
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.
- chrisweekly 10y ago
  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.

hoodoof 10y ago

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.

krrishd 10y ago
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
tomduncalf 10y ago
> 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
- ccallebs 10y ago
  Is there a resource you can recommend to get your head around all the basics?
  - acemarke 10y ago
    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. [0] https://webpack.js.org/ https://webpack.js.org/ [1] https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links [2] https://github.com/markerikson/react-redux-links/blob/master/webpack-tutorials.md https://github.com/markerikson/react-redux-links/blob/master... [3] https://github.com/markerikson/react-redux-links/blob/master/webpack-advanced-techniques.md https://github.com/markerikson/react-redux-links/blob/master...