module-federation-examples
single-spa
module-federation-examples | single-spa | |
---|---|---|
13 | 49 | |
5,253 | 13,036 | |
1.1% | 0.4% | |
9.8 | 6.1 | |
5 days ago | 14 days ago | |
JavaScript | JavaScript | |
MIT License | 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.
module-federation-examples
- Lazy load external library from CDN?
- How to create a "Container app" with navbar that is used to select other separate apps?
- Angular et micro front-end : conseils et à la recherche d'un bon tuto
- Do we really need module federation plugins for various frontend tooling ( e.g. vite, webpack etc)?
-
How to restrict code access in module federation?
Here is an example how that looks like.
-
Is it possible to use Module Federation at static sites built with cra npm build?
Personally, I would opt for the shared-components route. Check out this GitHub repo for a ton of config examples: https://github.com/module-federation/module-federation-examples
-
Implementing Micro Frontends in React Using Module Federation
Project Github Repo Webpack Documentation Module Federation Example Module Federation (official documentation)
-
How to Build a Micro Frontend with Webpack's Module Federation Plugin
Module Federation Examples by Zack Jackson
-
Next.js 11, Module Federation, and SSR — A whole new world
We have a primitive example of omnidirectional, distributed routing available on Github. module-federation-examples/nextjs at master · module-federation/module-federation-examples *Module Federation in Next.js depends on @module-federation/nextjs-mf It will not work unless you have access to this…*github.com
-
[AskJS] Webpack Module Federation - what if remote is not available?
Before using module federation on the product, I have the question same as you. I divided into module federation examples, finding webpack already provides a solution. It's called dynamic remote Please see here: https://github.com/module-federation/module-federation-examples/tree/master/advanced-api/dynamic-remotes
single-spa
-
Managing View State and Client-side Routing in SPAs
At JupiterOne, we've made a significant transition from a monolithic frontend to a distributed frontend architecture using microfrontends, powered by (single-spa-react)[https://single-spa.js.org/]. This architectural shift has brought many benefits, such as lazy loading sections of the app and accelerating our development cycle. However, like any significant change, it has also come with its set of challenges.
-
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. :)
[1] https://single-spa.js.org/
-
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.
What are some alternatives?
dynamic-container-path-webpack-plugin - Change 'publicPath' at run time rather than build time for dynamic module federated containers.
nx - Smart Monorepos · Fast CI
dynamic-host-module-federation - An environment-agnostic, federated host that consumes remote applications dynamically.
Bit - A build system for development of composable software.
slides - Presentations
qiankun - 📦 🚀 Blazing fast, simple and complete solution for micro frontends.
module-federation-angular
piral - Framework for next generation web apps using micro frontends. :rocket:
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
FrintJS - Modular JavaScript framework for building scalable and reactive applications
aegis-host - This is the ÆGIS federated application host. Federated components are independently deployable, written by multiple teams in multiple languages, and loaded from multiple repos and network locations at runtime, yet capable of running together in a single process or as distributed components in the ÆGIS application fabric.
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.