Hi Milad, In the scenario described above, would each smaller app (i.e., non > app-shell) also be bootstrapped for Angular 2 individually, or would the > bootstrapping only happen on the app-shell?
That depends on how you solve this. I would share the common components, but would create different SPA's that work alongside each other (main app in index.html, and then app-a.html and so on), That way you can navigate between the spa's by normal navigation, and all apps are fully self-contained. This way you are sure teams can't mess up outside their own part(s). Also this will keep memory pressure lower, as each team might have their own dependencies. This matters even when you do lazy-loading. (unloading isn't flaw-free..) Will the router be able to handle loading content (components/templates) > from external apps? Within limits, yes it can. Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
