The end: Create React App (2016-2025)

Publish Date: Feb 18

265 54

The Sunsetting of Create React App

On February 14, 2025, React officially deprecated Create React App (CRA), marking the end of an era for React developers. For years, CRA was the go-to tool for bootstrapping new React projects.

Why is Create React App Being Deprecated?

React ecosystem has evolved significantly since CRA’s introduction in 2016. Modern frameworks and build tools have surpassed CRA in both performance and flexibility. With no active maintainers and better alternatives available, the React team decided to retire CRA. The React team is encouraging developers to migrate to frameworks like Next.js or build tools like Vite.

Also because:

CRA does not provide a routing system
CRA lacks optimized data-fetching strategies
CRA ships apps as a single JavaScript bundle, which can result in longer load times. Modern frameworks automatically handle code splitting
CRA has lacked active maintainers

What now?

Starting today, developers installing Create React App will see a deprecation warning:

create-react-app is deprecated.

You can find a list of up-to-date React frameworks on react.dev
For more info see: react.dev/link/cra

CRA will still function in maintenance mode and has been updated to support React 19. However, no new features will be added, and developers are strongly encouraged to migrate to modern solutions.

How to Migrate Away from Create React App

You can visit the official guide at the React blog post here.

Final Thoughts

Our tip: If you're looking for the simplest and most efficient way to set up a new React project after Create React App's deprecation, React + Vite is the way to go.

What are your thoughts on this change? Let’s discuss in the comments! 🚀

Comments 54 total

Amir HusainFeb 19, 2025
React + vite or react + next which one is more future secure?
- Jayaraj ViswanathanFeb 20, 2025
  Definitely next js!!
- programORdieFeb 20, 2025
  For big projects nextjs, for quick testing or static pages vite
  - Nikola PerišićFeb 20, 2025
    Agree @programordie
- Nikola PerišićFeb 20, 2025
  Hello, Amir! I think it depends on your project’s needs. React + Vite is awesome for fast development. It's the best choice for SPAs & smaller projects IMO. On the other hand, React + Next is best for scalability because of it's server-side rendering(SRR) and static generation(SSG) and built-in routing. I don't think you can go wrong whichever one you choose. Thanks for the comment 🚀
- anscarlettFeb 21, 2025
  Webassembly
  - Nikola PerišićFeb 22, 2025
    For sure!
- SIVAPRAKASAM TMar 8, 2025
  vite is amazing for speed & simplicity, but Next.js is more future-proof. With React shifting towards Server Components & SSR, Next.js is leading the way
Sarfaraz ShaikFeb 20, 2025
It's sad that CRA is deprecated, but I'm excited to try Next.js and Vite for better one
- Nikola PerišićFeb 20, 2025
  Yes, it's sad. To be honest, I haven't used it in a long time. I remember using it when I started learning React.js. I always use React + Vite + Typescript. However, there is some nostalgia because the first React app I built was generated using CRA :(
  - Osman ZakirFeb 20, 2025
    I'm the same way. Using Next.js with TypeScript now, and React + TypeScript + Vite if Next.js isn't needed, but CRA still gives me nostalgia.
MD. Ariful IslamFeb 20, 2025
What about rsbuild?
- Nikola PerišićFeb 20, 2025
  If you prefer more flexibility, RSBuild is a good choice. If you prefer stability and larger ecosystem, go for Vite.
muwanguzi alvinFeb 20, 2025
Now where does this leave react native?
- Nikola PerišićFeb 20, 2025
  Hello! I have good news for you 🙂
  React Native remains unaffected by CRA's deprecaton because it has its own ecosystem.
  - Friday candourFeb 20, 2025
    Which is metro bundler
    - Nikola PerišićFeb 20, 2025
      Yep
      - Drew RileyFeb 21, 2025
        Metro with react 19?
Geoffrey SwensonFeb 20, 2025
You may as well add Vue to Vite and ditch React altogether :-)
- Nikola PerišićFeb 20, 2025
  Yes, I like Vue.js too 🙂
NerdherdFeb 20, 2025
Im coming from NextJS (used at work for an e-commerce platform), and have to say I'm really liking the simplicity of react-router v7 over the vastly many concepts you have to know in nextjs.
- Nikola PerišićFeb 20, 2025
  Like for example?
  - NerdherdFeb 20, 2025
    I like that:
    
    caching is just using http headers
    
    Back in NextJS 14, I had to run a bash script that would periodically delete cached images on my instance (it was a simple setup, since we didnt have time for a CDN)
    
    the only alternative was to use vercel that automatically handles the cached files back then, not sure if its the same now since ive not run latest nextjs in prod. I didnt like that we would be vendor locked in, especially for a small company.
    
    routing can either be explicit or via file/directory of your pages (using fs-routes)
    
    I personally prefer explicitness for routing for larger frontend projects
    
    client vs server side rendering is defined with a simple clientLoader function in a file that defines your page component
    
    it feels more natural to have it defined as a function to me vs having a 'use client' string defined in the page in NextJS
    
    React router provides SSR with actions
    
    the action functions visually breaks the page into key "segments" making it feel more "class-like"
    
    makes it easier for junior and mid-lvl engineers in my team to reason about , especially if they're new to frontend and need to work on simple CRUD dashboards for internal tools.
    
    NextJS has something similar to react-router's actions with getServerSideProps and getStaticProps, but I never managed to get the caching mechanism to work properly
    
    maybe my understanding was poor or did not learn the proper fundamentals of nextjs in the rush to build the web app
    - Daniel FriesenFeb 23, 2025
      You might want to revisit Next.js sometime. I don't know whether it'll be exactly to your taste. But Next.js' old pages directory API (the one with getServerSideProps) and the new app directory API are so different they might as well be completely different frameworks.
      
      Caching is still changing so you might want to wait, but it's already very different from what you remember. You are limited to file based routing, but having layouts changes things a lot. And stuff like getServerSideProps is completely replaced with React's new RSC components and Server Actions.
  - Hem DFeb 23, 2025
    I haven’t used Remix at work yet due to company needs but this should give some insight:
    remix.run/blog/remix-vs-next
Future_DeveloperFeb 20, 2025
Thanks for sharing. Am currently using react + vite, it performance is outstanding and awesome.
- Nikola PerišićFeb 20, 2025
  You're welcome! Yes, it's performance is awesome you will see.
Ryan WhealeFeb 20, 2025
Tanstack start is something to keep your eye on.
- Nikola PerišićFeb 20, 2025
  Yes! I used it to implement a frontend for a big bank in Serbia and it's awesome! The only negative issues I had were the integration tests. They are not yet supported.
  
  But be careful! It can use over 300KB of application bundle size.
  
  @designbyonyx
the_aceixFeb 20, 2025
Just deprecate react already. Vue is the better
- Nikola PerišićFeb 20, 2025
  I like Vue, but what are the key things because you think it's better?
  - the_aceixMar 6, 2025
    
    Stable API for devs, even across major releases with good backward-compatibility
    
    No major security issues
    
    Wayyy better dev tools (just look at Nuxt dev tools and Vue chrome extension)
    
    Flexibility in code style: Vue SFC, use Vue in MPAs, even the option to use tsx/jsx
    
    Styling is scoped within components. I don't know why React doesn't make this as simple as Vue
    
    oh.. and Vue guys can't relate with the react router drama
- Drew RileyFeb 21, 2025
  Omg 100%
  
  The slowest websites are all React.
  - Zach GoethelFeb 21, 2025
    I don't disagree. However, Blazor WebAssembly would like to talk to you ;P
    - Drew RileyMar 11, 2025
      I mean web assembly sure. But while I was waiting for blazor to download I moved over to a svelte run competitor.
Gad IradufashaFeb 20, 2025
Vue.js is the future, thanks to react!
- Nikola PerišićFeb 20, 2025
  Hahaha, RIP React developers. Just kidding, of course
Muhammad QasimFeb 20, 2025
Should i give up learning react ? 🤔
- Nikola PerišićFeb 20, 2025
  No, just learn it the right way. I suggest React + Vite + TypeScript + Tailwind + Sass
  - Muhammad QasimFeb 20, 2025
    Ahh i see, thank you so much
  - Rense BakkerFeb 25, 2025
    Disagree on learning tailwind and sass. Learn css, which is a transferable skill for the web and then have a look at any styling solution for react except tailwind 😛 I recommend pandacss.
    - Nikola PerišićFeb 25, 2025
      CSS must be known. That's the default. That's why I didn't mention it
      - Rense BakkerFeb 26, 2025
        You don't need to know any CSS for tailwind, which is already happening... People don't know how to do the simplest things with CSS, all they know is limited tailwind utility class names.
        
        Nikola PerišićFeb 26, 2025
        I would change it to: You don't need to know advanced CSS to use Tailwind
JFeb 22, 2025
It was only a matter of time. Use Next, Remix or Vite.

Don't waste your time with Vue.
- Nikola PerišićFeb 22, 2025
  React devs will be mad
  - JFeb 22, 2025
    Not really. I've worked with FAANG on several projects so I know exactly what the industry demands are. Vue is good for small apps, but anything serious and at large-scale then React is your best friend.
Muhammad UsmanFeb 22, 2025
🚀 Just finished my very first frontend challenge for Dev Community!

dev.to/web_dev-usman/discover-your...
Give your feedback there, and support me.
- Nikola PerišićFeb 22, 2025
  Sure! Have you tried scanning it using Dev.to Rater?
  - Muhammad UsmanFeb 22, 2025
    Just scanned, here are the results,
    SCORE
    8.04
    Score got cut off because of license for the code, I have copied and pasted it from CodePen.
    - Nikola PerišićFeb 24, 2025
      Nice! If you've issued a bug or want some additional feature, feel free to open an issue in our repository.
cc44599Feb 23, 2025
nice
Rense BakkerFeb 25, 2025
If only Nextjs would embrace vite as a bundler instead of webpack, the choices would be so simple.
NitayApr 6, 2025
The thing that I worried about is that two years ago I made a huge website for the company with cra
Now it's dead, and I need to change the whole website for Vite setup...so for developers, every two years we need to take a risk that the website we developed is no longer stable...like never

Add comment

Nikola Perišić @perisicnikola37