6 ms·

So thats why CRA has been left to die?

by hyfgfh 3y ago

dgellow 3y ago
What is cra?
- preommr 3y ago
  create react app: https://create-react-app.dev/ https://create-react-app.dev/
- deleted 3y ago
  [deleted]
azangru 3y ago
What's the connection? Also, take a look at this response from 2021: "Like I said earlier, it was always the intention that we're not going to be able to work on it full-time... [I]t was intentionally designed for this kind of sporadic development. We would get critical fixes out as soon as posible, but overall, starting with 2.0, it's mostly in maintenance mode and does not strive to be the best tool for production React apps. It is a tool to get started and get something running fast. Perhaps, it's not even best at that anymore." https://github.com/facebook/create-react-app/discussions/11768#discussioncomment-1817264 https://github.com/facebook/create-react-app/discussions/117...
- hyfgfh 3y ago
  A new solution could replace some of the tools we use today, making it obsolete and not worth maintaining in the future. Make sense, but the lack of an "oficial" solution doesn't help https://react.dev/learn/start-a-new-react-project https://react.dev/learn/start-a-new-react-project
  - gardnr 3y ago
    I have been tempted to go back to turn of the century tech: html tables for layout with inline css for styling and smarty template for separation of concerns all driven by php.
    - azangru 3y ago
      > html tables for layout with inline css for styling Html and css have only been getting better over the past two decades; they are not the problem; no need to resort to inline styles and tables. As for going back to server-side templating with php, this is a very good option.
fabian2k 3y ago
CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opinion. The config was too complex to eject and modify compared to what you could do yourself with Webpack directly.
- rozularen 3y ago
  I mean, the CRA repo is under facebook org in github
- unkulunkulu 3y ago
  my 2c: still does the job without ejecting on my small project. Just reading your comment made me happy I don’t spend time thinking about webpack configuration
  - fabian2k 3y ago
    Until you run into any problem that you need to debug with the build process. And there are more problems today because CRA is not maintained well now. The tools got much better, it's much easier to just set up a basic Webpack or Vite setup today compared to when CRA was originally created. And the simple configs are much simpler to debug and understand when something doesn't work as expected.
    - unkulunkulu 3y ago
      thank you, will keep this in mind if problem arises, maybe the best route would be to reset the build system
- hyfgfh 3y ago
  > CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opinion. The config was too complex to eject and modify compared to what you could do yourself with Webpack directly. Yes agree, but writing and marinating config for multiple projects just don`t scale. Not to mention we need something dirty and fast.
tiborsaas 3y ago
I recommend Vite starter templates: https://vitejs.dev/guide/#scaffolding-your-first-vite-project https://vitejs.dev/guide/#scaffolding-your-first-vite-projec...

So thats why CRA has been left to die?

by hyfgfh 3y ago

So thats why CRA has been left to die?

dgellow 3y ago

What is cra?

preommr 3y ago
create react app: https://create-react-app.dev/ https://create-react-app.dev/
deleted 3y ago
[deleted]

azangru 3y ago

What's the connection? Also, take a look at this response from 2021: "Like I said earlier, it was always the intention that we're not going to be able to work on it full-time... [I]t was intentionally designed for this kind of sporadic development. We would get critical fixes out as soon as posible, but overall, starting with 2.0, it's mostly in maintenance mode and does not strive to be the best tool for production React apps. It is a tool to get started and get something running fast. Perhaps, it's not even best at that anymore." https://github.com/facebook/create-react-app/discussions/11768#discussioncomment-1817264 https://github.com/facebook/create-react-app/discussions/117...

hyfgfh 3y ago
A new solution could replace some of the tools we use today, making it obsolete and not worth maintaining in the future. Make sense, but the lack of an "oficial" solution doesn't help https://react.dev/learn/start-a-new-react-project https://react.dev/learn/start-a-new-react-project
- gardnr 3y ago
  I have been tempted to go back to turn of the century tech: html tables for layout with inline css for styling and smarty template for separation of concerns all driven by php.
  - azangru 3y ago
    > html tables for layout with inline css for styling Html and css have only been getting better over the past two decades; they are not the problem; no need to resort to inline styles and tables. As for going back to server-side templating with php, this is a very good option.

fabian2k 3y ago

CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opinion. The config was too complex to eject and modify compared to what you could do yourself with Webpack directly.

rozularen 3y ago
I mean, the CRA repo is under facebook org in github
unkulunkulu 3y ago
my 2c: still does the job without ejecting on my small project. Just reading your comment made me happy I don’t spend time thinking about webpack configuration
- fabian2k 3y ago
  Until you run into any problem that you need to debug with the build process. And there are more problems today because CRA is not maintained well now. The tools got much better, it's much easier to just set up a basic Webpack or Vite setup today compared to when CRA was originally created. And the simple configs are much simpler to debug and understand when something doesn't work as expected.
  - unkulunkulu 3y ago
    thank you, will keep this in mind if problem arises, maybe the best route would be to reset the build system
hyfgfh 3y ago
> CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opinion. The config was too complex to eject and modify compared to what you could do yourself with Webpack directly. Yes agree, but writing and marinating config for multiple projects just don`t scale. Not to mention we need something dirty and fast.

tiborsaas 3y ago

I recommend Vite starter templates: https://vitejs.dev/guide/#scaffolding-your-first-vite-project https://vitejs.dev/guide/#scaffolding-your-first-vite-projec...