Looking for advice on building an Angular shell that integrates independent micro-apps—with their own dependencies—featuring a header, footer, and content area while preserving each app’s native routing.
hey flyingeagle, i tried using a router gateway that sends control to each microapp so routng conflicts are minimized. makes dependency isolation easer even if its a bit tricky
hey there, im exploring similar micro fronend strategies. i found that isolating dependencies with lazy loadng microapps works well. how do you handle potential route conflicts between apps? curious about your experience!
In my experience, ensuring robust communication between the Angular shell and micro-apps is pivotal for seamless integration. Using a shared event bus can help synchronize state transitions without compromising each app’s native routing. I found that applying Angular Elements for micro-app encapsulation not only maintains dependency isolation but also simplifies loading processes. Testing in isolated environments before integration further mitigates potential routing conflicts. A methodical approach to performance monitoring and error handling is beneficial, as even minor misconfigurations can lead to unpredictable behavior in production.
hey all, ive been tinkering wit dynamix routing when integrating microapps and hit some odd conflicts. im curiouz abt the value of central routing vs letting each microapp self-route. anyone experiemced this approach? what workd best for your integration?
hey all, i built a micro-frontend in angular letting each micro-app manage its own routng. used a common loader for shared deps. works fine so far, though i had to tweak a few things to keep conflicts at bay