fkolar / microfrontend-st Goto Github PK

In this repo https://github.com/fkolar/microfrontend-st/tree/master/module-federation-apps/apps/common-req-app when I try to expose local simple component (DownloadComponent) all works but not sure about sharable npm angular modules?

For example like this ?

exposes: {
          './Download': './apps/common-req-app/src/app/download.component.ts',
          './CommonReq': require.resolve("@aribaui/common-req-app")
}

We need to support page-2-page navigation (macrofront-end level as Manfred calls this ) but also support complete page mix up ( microfront-end different component from different team on one page).

We try to develop right now component in isolation, so developer can now rely as much as he can on standard angular-cli process microfrontend-apps/libs and have the other two repos for creating remote & host module fed. apps.

Like on above picture.

1BX App Team

• Assemble final microfrontend app from different features

Framework Team

• Responsibel for providing an AppShell (page layout, shellbar, ....) and set of API

Angular Lib Development

• Microservice team develops a pages/components. They are shared as npm modules as microfrontend is not only consumer

Angular Webpack development

• This where we want to take feature developed by above team and expose it as module federation remote.

Questions:

1. Right now we are relying on @manfredsteyer work angular 9 and some patched libraries
   Q: What if. './CommonReq': require.resolve("@aribaui/common-req-app") is developed and deployed to npm in angular 10? Version conflict.

2. When you look at DownloadComponent (module-federation-apps/ ), this is really simple remote and really elementary usecase which will never be the case in real app.
   Q: What if I want to share a component and this has other depenencies? Then in Angular you need whole module to be imported. , then probably sharing just a simple component is out of question.

   • Should we use Modules with Routing and on the Final assembly app (one-bx-app) use named router-outlets ?

Q: How do you import dynamically Specific Module from the npm package? Something like you would do with imports ?
->import {MyFeatureModule} from '@aribaui/common-req-app'