-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Will Create React App be updated in the future? #13289
Comments
yes, more clarity on that is a must! |
Still, waiting for clarity on this? |
I have read a few times that CRA is no longer actively maintained, but not through official channels. CRA is also no longer mentioned in the React documentation. We have since moved away from CRA and switched to Vite. The move was relatively straight forward. |
yeah, I also did that move, using Vite now. :) |
Where I can see the vite documentation now the react docs does not have vite in it, it only has Next and remix in it. |
@usamamashkoor https://vitejs.dev/. To upgrade my app, I followed this blog post. I develop a project with +700 components and in my old laptop (a top tier 2017 macbook-pro) vite was painful slow. Webpack took 3-5 min to start, but at least after that I was able to work. |
Thanks I really appreciate your reply 😊 |
Create React App is pretty much dead, and the whole framework-design isn’t state of the art anymore. I recommend everyone to run away as soon as possible from Create React App, unless you are trapped into a legacy codebase. |
I think this issue not being addressed since 2 months has it's implications.
or something like that. |
I noticed that this project has not been updated for almost a year, and the official React documentation no longer mentions using Create React App to create React projects. I'm wondering if Create React App will still receive updates in the future?
If it will no longer receive updates in the future, or enters a so-called "maintenance mode", then I will use other frameworks to develop my React projects.
The text was updated successfully, but these errors were encountered: