react-redux-universal-hot-example VS create-react-app

I am developing an app based in this React Redux boilerplate. In one component I need to get the current URL when component is mounted in order to generate a shareable URL for social media. Than component is being accesible from dynamically generated URLs with React Router. In client side I wouldn't have any problem by getting it through javascript document object but the problem lies server side.

export default class ApiClient { constructor(req) { /* eslint-disable no-return-assign */ methods.forEach((method) => this[method] = (path, withCredentials, { params, data } = {}) => new Promise((resolve, reject) => { const request = superagent[method](formatUrl(path)) if (withCredentials) { console.log('first of all, its true') console.log(this) } if (params) { request.query(params) } if (__SERVER__ && req.get('cookie')) { request.set('cookie', req.get('cookie')) } if (data) { request.send(data) } request.end((err, { body } = {}) => { return err ? reject(body || err) : resolve(body) }) })) /* eslint-enable no-return-assign */ } /* * There's a V8 bug where, when using Babel, exporting classes with only * constructors sometimes fails. Until it's patched, this is a solution to * "ApiClient is not defined" from issue #14. * https://github.com/erikras/react-redux-universal-hot-example/issues/14 * * Relevant Babel bug (but they claim it's V8): https://phabricator.babeljs.io/T2455 * * Remove it at your own risk. */ empty() {}} I want to connect this to my auth so that I can prepend headers to protected endpoints, like so:

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.

The application was created with Create React App, a JavaScript library for building user interfaces. I separated the different moving parts of the application and put them into the following React components.

1. Run a Final Test: Make sure your app works as expected locally by running: npm run dev If it was created with Vite. npm run start If it was created with Create-React-App.