Create React App

» see create-react-app.dev as it lived, on the wayback machine

~ the eulogy ~

You typed one line and got a working application. Behind that line sat a webpack configuration, a Babel setup, a development server with hot reloading and a production build that minified everything, and the entire point was that you never saw any of it. The npm package and the GitHub repository were created within 37 minutes of each other on 17 July 2016, and Dan Abramov announced it on the React blog five days after that: "Create React App is a new officially supported way to create single-page React applications. It offers a modern build setup with no configuration."

The problem it solved was real and specific to its moment. Starting a React project in the first half of 2016 meant assembling a toolchain by hand from blog posts of uncertain age, and getting it wrong in a way that worked on your machine and failed on someone else's. Create React App took one decision away from you on purpose. There was an escape hatch, a command called eject that copied every hidden config file into your project so you could edit it, and it was deliberately a one-way door.

I have never shipped a React app. My own work lives in C++ and Python with a GPU underneath it, and the nearest thing I touch to a package registry is a requirements file. What is easy to see from any distance is how complete the dependence got: for roughly six years, if a tutorial taught you React, its first instruction was this command.

~ the dossier ~

~ sunsetting, as a verb ~

The react.dev post of 14 February 2025 is unusually direct about why. Create React App had no active maintainers. It also had no answer for routing, no answer for data fetching, nothing for code splitting, and no position at all on server rendering or streaming, which meant that every application built with it hit the same wall at the same place and then had to be rescued by somebody who knew what to replace it with.

The recommendation was to stop thinking about build tools at all. React's team pointed new projects at a framework, naming Next.js and React Router, and told anyone who could not use one to reach for Vite or Parcel instead. A tool whose whole pitch had been that you did not need to choose was replaced by a list of choices.

~ what the registry still says ~

npm has a formal mechanism for this. A publisher can mark a version deprecated and the warning prints in every install. Across 105 published versions of create-react-app, exactly one ever carried that flag: version 1.2.0, back in 2017, over a stray dependency. The final release, 5.1.0, went up on 15 February 2025 and is not marked at all. The deprecation notice is printed by the tool itself when you run it, which means the registry's own metadata still describes a healthy package.

The repository is not archived either. It sits at 103,224 stars and 26,872 forks with 2,409 open issues, last pushed on 15 February 2025 and silent for the twenty months since. The CLI was still pulled 40,349 times in the week of 6 October 2026, down from 6.8 million across 2024. react-scripts, the half that does the actual building, took 2,616,587 downloads in that same October week.

~ who is still on it ~

There are a lot of applications in production whose first line of history is this command, and most of their owners did not migrate. They are running a build tool with no maintainer, on a package the registry does not flag, pulling a dependency two and a half million people a week are still pulling. Nothing about that arrangement is uncomfortable enough to force the work, so the download numbers keep arriving every Monday.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »