Should I "still use" create-react-app? #12644
Replies: 2 comments 1 reply
-
I wanted to share my experience using Create React App (CRA) on a recent project. I must say that CRA feels like an integral part of React development, seamlessly integrating into the ecosystem. I've explored alternatives like Vite and Next.js, but while they have their merits, I find that CRA perfectly meets my project requirements and aligns well with my personal preferences. It feels familiar, comfortable, and reliable. Of course, I understand that different tools have different strengths, and it's always good to stay open to new possibilities. If it is possible, I'm excited to see how CRA evolves in the future and how it continues to empower React developers. |
Beta Was this translation helpful? Give feedback.
-
Create React App is no longer recommended by facebook documentation and so whilst not officially 'deprecated' it no longer seems to be getting active development from maintainers. |
Beta Was this translation helpful? Give feedback.
-
Why ask this question?
With tools like vite, frameworks like remix and nextjs getting popular, I think that the answer to the question itself is a big no. While existing projects use create-react-app, it's still fine using it. But, if you are creating a new project, I think the relevance of using create-react-app is gone.
Why is it irrelevant?
What are the solutions and the problems that create-react-app gives?
Solution cra gives
Problem cra gives
In 2022, a lot of problems create-react-app solves is already solved by some frameworks like nextjs and remix by giving you a loosely opinionated way to make react apps. While integrating tests is not a problem anymore. While problems with create-react-app like waiting for changes have already addressed by tools like vite and nextjs.
But what do you guys think? In my opinion, using create-react-app is like using tools from the stone age.
Beta Was this translation helpful? Give feedback.
All reactions