CRA has been deprecated, what now?

[Alevale]

As you can see in the official docs, CRA has been deprecated what does that mean for this package, and is there any kind of support going to be provided for the coming time?

If you want to put it in a more poetic kind of way, like many couples that split on valentines day, it seems like React and CRA chose that date to finally split ways after years of fighting to see if they could survive. Their love will be remembered, and their children (CRACO and others) will have to learn to live by themselves 😝

[dilanx]

Lmaoo what a poetic time indeed. It was about time tbh. I've been using other frameworks myself for a while now since they're a lot faster and more feature rich.

I'll try to fix some of the reported bugs to let CRACO continue to support existing apps, but there are no plans to release any major updates to this package since it was built to solve issues that specifically CRA had. Most newer frameworks support what CRACO does out of the box.

[spencer1573]

so would you say in 2026 if i'm needing to update an old codebase from react-scripts instead of using craco .. it would make more sense to move to vite or something newer like vite?

i am very aware that there could be side effects from jumping from react scripts to vite... but i feel like a lot of the new updates to libraries would play better with something like vite. and it doesnt have to be vite.

i think its great you made craco bytheway, and obviously it has served its purpose.

@dilanx

[marabesi]

@spencer1573 I have moved from craco successfully and I am trying to report the steps here: https://marabesi.com/2026/02/23/migrating-from-craco-to-vite.html