Course contentsShow
← React
Lesson 49 of 2,3962. Setup and Modern ToolingFree lesson

Create React App: The Legacy Standard

Understanding CRA's historical role, why it's no longer recommended, and when you might still encounter it.

Create React App: The Legacy Standard

What you'll learn: Why Create React App (CRA) was once the official way to start React projects, and why it's been superseded.

The Rise of CRA

For years, Create React App was React's official starter toolkit. Created by Facebook (now Meta) in 2016, it solved a painful problem: setting up a React project required configuring Webpack, Babel, ESLint, and countless other tools—a daunting task for beginners.

CRA hid all that complexity behind a single command: npx create-react-app my-app. You got a working React environment instantly, with zero configuration. It was brilliant for its time.

Why It Fell Behind

CRA used Webpack as its bundler, which works but is significantly slower than modern alternatives like Vite. As projects grew, developers faced:

  • Slow startup times (sometimes 20-30 seconds)
  • Sluggish hot reloading compared to Vite's instant updates
  • Outdated tooling as the project became harder to maintain
  • No built-in server-side rendering support

In 2023, React's official documentation removed CRA from its recommendations, pointing developers toward Vite and modern frameworks instead.

When You'll Still See It

You'll encounter CRA in:

  • Legacy codebases from 2016-2023
  • Older tutorials and blog posts
  • Corporate projects that haven't migrated yet

If you join a team maintaining a CRA project, you'll recognize it by the react-scripts package in package.json and commands like npm start that take longer than you'd expect.

Key Takeaway: Create React App was the gold standard for beginners but has been replaced by faster, more modern tools like Vite—though you'll still encounter it in existing projects.