create-react-app

Hi! I played a major part in getting that "installation" page rewritten to actually mention other tools like Vite :) The general TLDR is: - CRA was listed in the _old_ docs site - The new docs site coincided with the React team emphasizing "frameworks" to provide an all-in-one build experience and hopefully lead to better apps. - That also meant no ala-carte build tools were listed. This made many people (including me) unhappy. - CRA broke when React 19 came out in Dec 2024. This caused problems for beginners. - I pushed the React team to both deprecate CRA and finally rewrite the setup pages to list other build tools as valid options. I wrote up a much longer background of what happened around the "frameworks" push and this docs page here: - https://blog.isquaredsoftware.com/2025/06/react-community-20... And here's the issue I filed push

Yesterday I stopped hating AI because it converted an old webpack project with impenetrable plugin settings to a single simple Vite config. I still don't understand how people used to think scripts like this are the proper way to bundle an app. https://github.com/facebook/create-react-app/blob/main/packa... vite is great, is all I am saying

I could totally see how you'd arrive there. Backstory: create-react was a starter boilerplate for React built and maintained by Facebook. This was when webpack was the standard and just getting a local development environment to "hello world" for React could be challenging.[1] That project was depreciated and the popularity of the Next.js site framework for react projects (plus I certainly assume heavy lobbying from Vercel) pushed the react docs to officially suggest create-next as the new starting point.[2] Note that there are many other ways to start a react project and there are also many react projects that don't use or need Nextjs. (I use react quite a bit but I pair it with Astro.js, for example.) I would say that a lightweight Vite template is really all you need for a lot of early success with a local environment for learning / bu

Pleased to say I had a meaningful hand in this :) As some background, this finally happened because: - React 19 broke CRA - I griped about it loudly on Bluesky (https://bsky.app/profile/acemarke.dev/post/3lggg6pk7g22o) and that started a long debate - I filed an umbrella issue describing the specific breakage and recommending an actual official deprecation announcement (https://github.com/facebook/create-react-app/issues/17004) - The React team finally took action to fix the CRA breakage, then wrote the blog post, updated the setup docs page, and redid the docs SEO to get Google to stop showing the legacy docs as a search result. So, kudos to the React team for making meaningful changes here! (It's not _exactly_ what I was hoping for, and I gave them some additional review feedback that they didn't include, but gotta give credit for the

Create React App should not be used because it is no longer maintained. Here is its GitHub repro: https://github.com/facebook/create-react-app/commits/main/ . It has had very few updates since July 2022. This is bad because it needs constant updates because it depends on a large number of packages and those packages are constantly releasing security updates.

This is just a discourse based on "I need to churn out something, I need that fast and I didn't start in the web game when Backbone and E4X were solid corporate choices". If you are not in a hurry, work in a solid team and have a good attention span, a lot of clickbait idiocy around JS may not happen. It's just that the lone inexperienced guy is one of millions inexperienced guys who are taught the wrong ways everyday. I'm presenting you one of countless examples: a lot of coding bootcamps teach React, maybe with TS, maybe with JS. Enter react-create-app. https://github.com/facebook/create-react-app The docs are a link, while the commands you can copy and paste are laid out at 9th row in the README. That will become a habit for a junior.

What's the connection? Also, take a look at this response from 2021: "Like I said earlier, it was always the intention that we're not going to be able to work on it full-time... [I]t was intentionally designed for this kind of sporadic development. We would get critical fixes out as soon as posible, but overall, starting with 2.0, it's mostly in maintenance mode and does not strive to be the best tool for production React apps. It is a tool to get started and get something running fast. Perhaps, it's not even best at that anymore." https://github.com/facebook/create-react-app/discussions/117...

Can you be more specific which linting rule you're talking about for the sake of readers who may be unaware, and perhaps mention how this completely solves this problem? Because 1. a linting rule does not absolve this from being a footgun and 2. if you're talking about 'exhaustive-deps' there are many cases where following the linter here has caused infinite render loops among newbies across multiple teams I've worked with. Also see this highly contentious thread: https://github.com/facebook/create-react-app/issues/6880

CRA affected: https://github.com/facebook/create-react-app/issues/13171 and everyone whose production build depends on it.

Seems you are right. More context here: https://github.com/facebook/create-react-app/issues/13077

Last I checked the "unfixed vulnerabilities" where regex Denial Of Service at build time, see https://github.com/facebook/create-react-app/issues/11174

Interesting that CRA isn’t mentioned anymore. Someone opened an issue to discuss this: https://github.com/facebook/create-react-app/issues/13072