single-spa
Bit
Our great sponsors
single-spa | Bit | |
---|---|---|
48 | 69 | |
13,017 | 17,546 | |
0.6% | 0.7% | |
6.3 | 9.9 | |
1 day ago | about 10 hours ago | |
JavaScript | TypeScript | |
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.
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.
-
Single-SPA and Svelte advices.
You got me curious and I found that single spa is something new to me - if I read https://github.com/single-spa/single-spa then I reckon you can use Svelte(Kit) in such framework - like you can use angular etc
- 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
-
Vue 2 EOL
You may want to look into using single-spa to run Vue 2 and Vue 3 side by side while you're migrating. Once your app is fully converted, you can stop using 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.
Bit
-
Theming using CSS Variables? Turn Them into VS Code Snippets for Faster, Error-Free Coding
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 are Dying: What’s Next?
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.
-
Composable Software Architectures are Trending: Here’s Why
The following diagram showcases how bit shows the dependency graph of modified components and their dependents.
-
Micro Frontends with Vite and Bit
This tutorial demonstrates how to build a micro frontend application using Vite and Bit.
-
Implementing a Service Oriented Architecture in 2024
Bit: A next-generation build system for composable software.
-
3 Principles for Component-Driven Development
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.
-
How To Build a Node.js Express App in Under 5 Minutes?
And one such tool that I've found that supports this component-driven approach is 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.
What are some alternatives?
nx - Smart Monorepos · Fast CI
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
qiankun - 📦 🚀 Blazing fast, simple and complete solution for micro frontends.
piral - Framework for next generation web apps using micro frontends. :rocket:
Commander.js - node.js command-line interfaces made easy
FrintJS - Modular JavaScript framework for building scalable and reactive applications
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
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.
Next.js - The React Framework