Hi Paitum, Depending on how your projects/teams are organized, different demands are coming into play. A monorepo is a solution, but it doesn't work for everyone. reading this back, I think your situation does not really fit the mono-repo workflow. (Still, this would solve quite some problems. Yarn workspaces and NX are tools that make it easier, but GitHub might not provide the granularity you need in access rights and so)
If I was in your place, I would hand each team a set "shell" in where they can provide their lazy-loadable modules or Angular-elements. (the later would have my preference, and opens up the door to a more flexible integration path) The shell will provide the company width things (usually auth, and access to certain DB's that most (if not all) teams need. This requires a sing;e angular version but updating from 6 or 7 to 8 should not be a big deal. For deployment, you use a souped-up shell, that is capable to instantiate every team's module. (if those are elements, its really loading the script, and add the element to the page.) Angular Elements are an excellent solution for portals. But make sure you set the requirements for the outlets/widgets/pages/whateverYouCallt are clear. (simple sample, for a widget you might say x and y size is max 300px, and should be an increment of 50, so it fits the'grid') The build story for angular elements will improve a lot, but it is already usable for the situation you are in now. -- 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/deba67c5-04c8-40b0-b8c7-37ba5b2d4e89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
