react-boilerplate VS create-react-app

I worked on a React project in 2019, I believe it was built on top of the react-boilerplate template, and the developer experience with Redux was so bad that I became a Vue developer.

Clone this repo using git clone --depth=1 https://github.com/react-boilerplate/react-boilerplate.git

10. React Boilerplate

2 React Boilerplate is a reliable and well-designed boilerplate in the Javascript UI Libraries, with 28.2k ratings on GitHub. The super-rich component and font base, together with Redux, Mocha, Redux-Saga, Jest, React Router, PostCSS, and reselect are all included. They support SEO indexing. Concentrating on app development and performance is more than enough.

React Boilerplate is a fantastic tool for setting up a React project. On its main page, React Boilerplate touts its accessibility through its app even with no network connection and positions itself as the future of fast web apps.

We are using https://github.com/react-boilerplate/react-boilerplate and have a classic store layout with multiple components.

I'm working on an app with a login page and the rest of the pages of the app (should be logged in to view). I'm using react-boilerplate. From this example, I edited my asyncInjectors.js file to have redirectToLogin and redirectToDashboard methods:

I'm working on application using a Web API(asp.net core) and a SPA (react-boilerplate). I'm starting work in user registration/login and one of the requirements is to allow for user to sign in with facebook, google, etc

React.js Boilerplate :

I used create-react-app and removed the boilerplate to start a blank application. The goal is to search a user with https://api.github.com/users/ and present the result.

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 / building with React.

[1] https://github.com/facebook/create-react-app

Setting up a ReactJS app can be done using different methods. Developers have various options ranging from using create React App (CRA), using Vite, or any other method they are familiar with. Once the ReactJS app is integrated, installing Tailwind CSS as a dev dependency is pretty straight forward. The guide provided in the Tailwind CSS documentation is easy to read and quick to understand let’s break down the steps.

My website's previous iteration was built in 2021. It was bootstrapped using (the now deprecated) Create React App and it took approximately 2 months to build. The home page included a bunch of photos that I had taken myself of my desk and keyboard as background for several sections and it included most of the information on the website. In the middle of the page I put the SkillsTerminal (which also features in the current version), which provided visitors with a familiar and mobile-ready UI which included my tech skills, aswell as a bit of information on my work and project history.

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 actual changes and steps forward!)

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.

Not so fast, though. V0 uses shadcn, which isn’t fully compatible with Create React App.

Don’t use Create React App: It’s outdated, slow, and lacks extensibility.