is CRA deprecated

[Ali-Milani-13]

I see lots of articles and YouTube videos talking about CRA is dead and this is why React.dev doesn't recommend it anymore. people are switching to Vite.
but for me Vite is unstable, and you have to configure everything yourself which is time consuming.
I noticed that React.dev don't recommend Vite either. it just recommends Remix,Next and Gatsby.

so.

is CRA is dead or I can still use it? because it feels good and easy to use it.

[SRICKKY]

CRA isn't dead, we can still use it to generate react projects!

You can use this link

[srinivasan-r23]

Refer this official docs…
https://create-react-app.dev/docs/getting-started

[Gravy59]

for me Vite is unstable

How is vite unstable, exactly? It's a mature project.

you have to configure everything yourself

Vite has official templates for react: npm create vite@latest my-react-app -- --template react. Even in those templates, the only configuration needed is this:

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react-swc'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
})

to load the react plugin.

[Zwyx]

Vite doesn't seem unstable at all to me. I've been using it for a few projects, I'm very happy with it. I think it's the best way these days to make a simple SPA with React (but if you need more features, go with Next or Remix).

[Ali-Milani-13]

the problem with CRA is being minimal. you have to configure module bundler all the time.

CRA have everything preset. I never needed to configure it until recently and I did it with react app rewired. easy.

I didn't have good experience with Vite. it was frustrating

[simod]

@Ali-Milani-13 I was as happy as you with react app rewired, but as last week it stopped building, it just stays stuck forever in "optimizing production build", this with docker node based image. I was therefore trying to use another framework. Did you manage to keep using CRA? ty

[Ali-Milani-13]

@simod I only needed copy-webpack-plugin and it works. I don't know if you need so much configuration.

I created a config-overrides file and this is how I used it :

const CopyPlugin = require("copy-webpack-plugin");


module.exports = function override(config, env) {
 

  config.plugins.push(
    new CopyPlugin({
      patterns: [{ from: "src/config.js", to: "env.js", force: true }],
    })
  );




  return config;
};