DEV Community

The end: Create React App (2016-2025)

Nikola Perišić on February 18, 2025

The Sunsetting of Create React App On February 14, 2025, React officially deprecated Create React App (CRA), marking the end of an era f...

Read full post

Amir Husain • Feb 19

React + vite or react + next which one is more future secure?

Nikola Perišić • Feb 20

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 🚀

programORdie • Feb 20

For big projects nextjs, for quick testing or static pages vite

Nikola Perišić • Feb 20

Agree @programordie

Jayaraj Viswanathan • Feb 20

Definitely next js!!

Sarfaraz Shaik • Feb 20

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

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 Zakir • Feb 20

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.

muwanguzi alvin • Feb 20

Now where does this leave react native?

Nikola Perišić • Feb 20 • Edited

Hello! I have good news for you 🙂
React Native remains unaffected by CRA's deprecaton because it has its own ecosystem.

Friday candour • Feb 20

Which is metro bundler

Nikola Perišić • Feb 20

Yep

Drew Riley • Feb 21

Metro with react 19?

the_aceix • Feb 20

Just deprecate react already. Vue is the better

Nikola Perišić • Feb 20

I like Vue, but what are the key things because you think it's better?

Drew Riley • Feb 21

Omg 100%

The slowest websites are all React.

Ryan Wheale • Feb 20

Tanstack start is something to keep your eye on.

Nikola Perišić • Feb 20 • Edited

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

Future_Developer • Feb 20

Thanks for sharing. Am currently using react + vite, it performance is outstanding and awesome.

Nikola Perišić • Feb 20

You're welcome! Yes, it's performance is awesome you will see.

Muhammad Qasim • Feb 20

Should i give up learning react ? 🤔

Nikola Perišić • Feb 20

No, just learn it the right way. I suggest React + Vite + TypeScript + Tailwind + Sass

Muhammad Qasim • Feb 20

Ahh i see, thank you so much

Nerdherd • Feb 20

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

Like for example?

Nerdherd • Feb 20 • Edited

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