This is in fact a full-blown monorepo experience, while each module is independent.Įvery single component you make (i.e. In your apps, every component and even the app component itself are developed, versioned, managed, published, developed, tested and built separately and all dependencies are managed. Any app can be a dependency on other apps. Apps are also “micro frontends” and support singlespa, module-federation, ESM and UMD to build MFEs from components and compose them in runtime. W ith Bit you can manage many apps in a single workspace, where each app may have it’s own stack, without complex CI and build setup: No need to configure per-repo ci pipelines.

There will be a lot of boilerplating and configs to make, but since you’re the one doing it you can make it fit your exact use case and needs. Since React is a library and not a framework like Angular, you will naturally have to add the tools and solution you need to build a full-blown production ready application. You can simply create a new React app without anything else.

Please feel free to comment and ask or suggest anything below. I hope it will help you on your journey to build a React application that will make you happy, and save time and mistakes in the process. Some of them serve a small website and optimize for fast ramp-up, some are for global scale, and some are both. In this article I’ve rounded up some of the best ways, frameworks and tools for creating a new React application. The more scalable and rich your application should be in technology, integrations, features, and people working on it - the more important it is to choose a foundation that will not just let you start easily, but will serve your needs down the road and allow your application to grow.

The decision on how to create a new React application need to be made in light of your end goal - are you building a full-blown web product? A marketing site? Will there be heavy engagement with the server? How many developers will be working on this app? Should it contain components you already have in other applications and want to use? How will it be built and deployed? and so on. Not just because you’ll have to work hard, but mainly because you have some key decisions to make that will affect your ability to scale, collaborate, and make this app work with the tools and needs you use today - and in the future. Creating a new React application is not a simple task.

React app examples