Migrating front-end only from CRA
Unanswered
Netherland Dwarf posted this in #help-forum
Netherland DwarfOP
I hope this community can help me navigate a migration from CRA to the current
I chose
My new apps need to work well with my existing technology landscape. This means at least the following:
* Host all this on my own systems (as opposed to
* Use the
* The front-end must be compatible with existing and new
* Use
* Use Apache for all
* I need to continue using environment variables for most configuration
*
* Continue using
All of this runs on several robust AWS EC2 instances that each run current versions of Rocky Linux. I use
I invite guidance from this community about things to seek out and things to avoid as I work through the apparently excellent documentation provided here.
react.dev ecosystem.I chose
Next.js because I very much want to preserve the yarn build behavior of CRA. When the front-end is finished, I want to deploy it into my existing server(s). My understanding is that this alone rules out vite. My read of the current (29-Aug-2023) react.dev site is that Next.js is the most appropriate choice for me.My new apps need to work well with my existing technology landscape. This means at least the following:
* Host all this on my own systems (as opposed to
vercel).* Use the
vscode remote debugging tools, specifically including launching the app in a Chrome browser* The front-end must be compatible with existing and new
node express services* Use
axios for all backend calls* Use Apache for all
https access to any deployed app on any of my systems* I need to continue using environment variables for most configuration
*
muiv5 for all front-end widgetry/rendering* Continue using
yarn rather than npm for most operations -- mostly because yarn is in my hands and scripts.All of this runs on several robust AWS EC2 instances that each run current versions of Rocky Linux. I use
vscode as my IDE, and all of my development is "remote" -- meaning that I rely on vscode-server. In my now-obsolete CRA/React projects, I rely on packages and scripts (in package.json) that use things like cross-env as well as environment variables already configured on each system and already used by the rest of my apps.I invite guidance from this community about things to seek out and things to avoid as I work through the apparently excellent documentation provided here.