Bit
single-spa
Our great sponsors
Bit | single-spa | |
---|---|---|
67 | 48 | |
17,465 | 12,987 | |
1.0% | 0.8% | |
9.9 | 6.3 | |
7 days ago | 16 days ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Bit
-
Micro Frontends with Vite and Bit
This tutorial demonstrates how to build a micro frontend application using Vite and Bit.
-
Monorepo, Poly-repo, or No Repo at all?
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.
-
React monorepo with open-source apps and proprietary libs
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.
-
How to Build and Publish Your First React NPM Package
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.
-
Warning, Streamlit collects a lot of data!
I am a backend developer, but in my brief experience with JavaScript frameworks, these opt-out telemetry services are more common in the JS ecosystem. The one I came across most recently was Bit
-
7 best ReactJS developer tools to simplify your workflow
Bit is a tool that helps developers to share and reuse React components across projects. It allows developers to create and manage a shared component library, making it easier to maintain consistency and improve productivity. You can visit its official website to learn more: https://bit.dev/.
-
Vue vs React: Which Framework Should You Choose?
Bit
- Vue Element Library on google chrome and other browsers
- [Docker] [VITE] [React] Rutas en Containers separados.
-
The minimal setup to package and reuse your React components
How do you share components between your projects? What do you do differently and why? Or do you use a service like BIT? Please let me know!
single-spa
-
Micro frontend frameworks in 2024
Single-SPA Framework - One of the most popular choices. It has a large community behind it and offers robust routing and lifecycle management for microapps. Ref - https://single-spa.js.org/
-
⏰ It’s time to talk about Import Map, Micro Frontend, and Nx Monorepo
Joel Denning is the visionary behind single-spa, boasting profound insights into the true mechanics of the web and is, in my view, a pioneer in micro frontend architecture. I highly recommend checking the single-spa website and his YouTube channel. While the videos might appear dated at first glance, rest assured, Joel is ahead of his time, and the content remains incredibly relevant today.
- Speed Run de MicroFrontends com Single-SPA (any%)
-
Use web components for what they’re good at
I’ve actually done that “web components as the interoperability layer”!
It was this old angular 1.8 app with new features being written in angular-hybrid-ized angular 8. Ripping out angular-hybrid and separating the angular 1.8 routes from the modern angular routes was difficult, but now they were totally separate.
The only thing linking them together was an object with some RXJS streams in it for state, and a little in-house wrapper “app” who just loaded one component or another depending on the URL and a hash of routes for config. (I’d probably use SingleSPA [1] now. Same thing really.)
We could deploy them separately since the build just ends up being another JS file somewhere that just gets included with a script tag at runtime. No version bumping! No big mega build!
We started replacing the remaining “old” routes 1 by 1 with a “new” counter part. That was the easiest part, and went at a pace devs were comfortable with (fast enough) and business folk could tolerate. (modular enough to not HAVE to be done all at once)
Last I checked, the angular 1.8 stuff is gone years ago. :)
-
Micro-frontend with Module Federations [Part 1] - Vite
Module Federation is not the unique solution, for example single-spa
- Angular et micro front-end : conseils et à la recherche d'un bon tuto
-
Building a Large Scale Micro-frontend Application.
Single-SPA and module federation are potent tools for building scalable micro-frontends. Single-spa provides a framework for building a modular front-end application. It allows lazy loading of micro-frontends, which helps improve the application's performance. In contrast, module federation enables communication and dependency sharing between different micro-frontends. It reduces code duplication, which can help with scaling an application.
-
How to split an Angular app into micro-frontend apps
Since micro-frontend allows us to develop applications individually, this also means you can use different frameworks and libraries together to develop each section of this application. Of course, this will have some advantages and disadvantages. If you are using different technologies to serve different parts of the application, it won't be so easy to move developers within teams. However, the door is open, and if you want to do something like that, you could use something like Single SPA, or some other, to help you organize and connect the different technologies into a larger application.
-
Micro frontends example
Using single-spa
-
Monolith to Module Federation at RazorpayX
There are numerous micro-frontend frameworks like Single SPA, Open Components, Mosaic, and so on The configuration for these tools can get complex and difficult to manage as we add more apps since they require configuration at each layer — routing, dependency management, and development. This would complicate our tooling and hence, would not work for us.
What are some alternatives?
nx - Smart Monorepos · Fast CI
qiankun - 📦 🚀 Blazing fast, simple and complete solution for micro frontends.
piral - Framework for next generation web apps using micro frontends. :rocket:
FrintJS - Modular JavaScript framework for building scalable and reactive applications
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Next.js - The React Framework
luigi - Micro frontend framework
Commander.js - node.js command-line interfaces made easy
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.