Hey everyone! I'm on the hunt for some GitHub repositories that feature real end-to-end applications using micro-frontends across Angular, React, and Vue. All I can find are basic setup demos, which is kind of frustrating. I'm curious about what holds people back from creating genuine micro-frontend projects. Is it because apps with different frameworks can't be integrated, or is there simply no compatible UI library? I'm specifically looking for something like a simple e-commerce app that includes features like home, search, product details, and checkout, while demonstrating how to manage styling, state, and communication between different micro-apps. If anyone has knowledge of a solid repo, or guidance on the best approaches to take, I'd really appreciate it! Thanks!
4 Answers
Most real-world implementations of micro-frontends are kept private because they are usually messy and heavily integrated with company infrastructure. The public repositories you see are often just demos due to the complexities involved in mixing frameworks like Angular and React.
For sure! No one wants to expose their complicated setups online.
Mixing multiple frameworks can lead to lots of issues with state management, styling, and communication between the apps. That's why you'll find most multi-framework examples are just demos. For something more practical, you could look at extending existing single-spa or Module Federation demos into your own project.
That's a smart approach! It lets you build upon working examples instead of starting from scratch.
Exactly, using those tools can really help with the architecture.
The reality is that multi-framework micro-frontends are best suited for very large projects, which are typically private and not meant for hobbyists. If you're looking to experiment, it might be better to keep it simple and stick with one framework.
That makes sense! Keeping the project manageable is key.
Right, and it’s often easier to maintain one system.
It seems like people usually avoid using multiple frameworks in a project, mainly due to the added complexity and larger bundle sizes. Most developers prefer to stick to one tech stack that handles everything without getting bogged down.
Totally agree! It just makes everything more manageable without needing to juggle different frameworks.
Yeah, using one framework simplifies architecture and reduces potential conflicts.
Yeah, I’d imagine the complexities would deter many from sharing publicly.