crisp-react VS nwb

Ability to handle a monorepo with 2 builds depends on a particular monorepo. For example, Crisp React (https://github.com/winwiz1/crisp-react) has 2 logical projects: server (https://github.com/winwiz1/crisp-react/server) and client (https://github.com/winwiz1/crisp-react/client). Each project can be built separately. And this is the website built (both projects used) and deployed automatically by Cloudflare Pages: https://jamstack.winwiz1.com

You can use Crisp React to split a monolythic React SPA into several SPAs. Each SPA will have its own instance of React Router that is aware of the several pages that belong to that particular SPA.

https://github.com/winwiz1/crisp-react/blob/master/docs/benc...

Tailwind is powerful, consistent and comprehensive but again the advantages come not without a drawback: In order to use it effectively one needs to learn/memorise yet another CSS. I have better things to do and think it's more efficient to use a set of CSS management approaches:

The alternative approach is to use not many but several tools in a manner that utilises advantages while minimising drawbacks. You can read about it here, scroll down to the CSS bullet.

You can have Login/authentication SPA, Reporting SPA, etc. Each SPA does its own routing as demonstrated here.

Crisp React demonstrates a variety of deployment choices.

Crisp React describes in detail several deployments of React app with Node:

If a React app can be logically split into several functional parts then consider splitting the app into several SPAs, each rendered by its own and smaller script bundle that loads faster. Each SPA will have its own Redux store. Crisp React can be used as a boilerplate.

You can split a large React app into miltiple SPAs that can be developed/tested separately. Crisp React facilitates this approach.

Running costs depend on workload (which dictates how powerful your cloud gear should be) and on redundancy (e.g. do you require your deployment to be resilient to any single VM or container failure). Basic setup for a containerised solution is very simple for all cases. For example, once you have a container, you can deploy to Heroku using steps described here and to GCP using this command.

Using nwb, you can easily set up a new React project with just a few commands, and you can quickly build, test, and deploy your application without having to manage complex configurations or dependencies yourself.