My organization runs a complex AngularJS-Angular-Hybrid portal that other teams contribute to. Having a large portal managed by various teams is unsustainable since everyone must move together as the platform evolves.
I have an idea where we breakup the monolithic portal into many portals which each share an "Application Shell". That way the user gets a single cohesive experience but is actually accessing different applications. I would like to write this Application Shell in Angular, but since it would be responsible for loading other Angular applications, it is unclear whether or not that would even work. Technically, the "Application Shell" should be agnostic to the content it loads, meaning that it should not interfere or conflict with the content implementation. *Does Angular support running multiple versions in a page?* e.g. Angular 6 and Angular 7, each controlling different DOM-trees. *If not, is there a way to work around limitations?* For example, if the reason it doesn't support multiple version is due to zone.js conflicting-- then can we simply work with Angular and manage our own change detection? *Do Angular Elements support running along side another Angular application?* We are exploring all of these questions ourselves, but I figured asking the community could be helpful. Many thanks. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. To view this discussion on the web visit https://groups.google.com/d/msgid/angular/dfe44e77-e44e-46c8-8daa-4002a7d91749%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
