Reactirator VS Bit

I am not too familiar with vite but I've explored a bit and as of today there are many developers promoting the use of vite instead of create-react-app to build React projects. The main argument in favor of vite is that it is blazing fast compared to CRA. I feel more and more concerned by the growing adoption of vite instead of CRA since I'm building Reactirator and I consider to add support for vite and maybe choose it as the default choice.

I am building Reactirator an opensource React project manager for some months now. I must admit I am kind of proud of my work because this is my first desktop application even if everything is far from perfect! For this reason I want to share my knowledges and what I've learnt by building Reactirator. Hence, I will be making posts in the future about how build some of the features of Reactirator. This will be detached from the Reactirator context because we won't use Electron, basically this will be a serie of mini react / node application.

Our demo solution was built using Bit, which allows us to create shareable components, render component “previews,” generate component docs, and so on.

UI libraries come with their own set of challenges, which greatly limit their effectiveness. These challenges stem from more fundamental problems related to code sharing and reuse. Let’s explore some of these challenges and examine how a new entity, the Bit component, addresses them.

The following diagram showcases how bit shows the dependency graph of modified components and their dependents.

This tutorial demonstrates how to build a micro frontend application using Vite and Bit.

Bit: A next-generation build system for composable software.

Bit drives a paradigm shift in the way we structure our software and collaborate on code. Its component-based approach produces more maintainable projects and more effective collaboration. However, the power of Bit is best harnessed when you adopt a certain mindset. This blog aims to guide you through the core principles and methodologies of building software with independent Bit components.

And one such tool that I've found that supports this component-driven approach is Bit.

This blog will explain how Bit can be used to implement any architecture and transform “fatal” decisions that seem too hard to change into decisions that are easy to make and change.

Oh can I address theses issues. I already looked at tools like Nx or Bit, but they aren't matching our needs with closed source libs.

To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.