Support for shared modules between NativeScript and Web

[VladimirMakaev]

One of the recommended way to build shared modules between NativeScript and Web is to use build time solution with conditionally using moduleName.module.tns.ts for NativeScript and moduleName.module.ts for web.

This is particularly needed in the scenarios when we share commonly used set of UI Components. E.g. we might wanna have a unified layer of components like: my-datepicker, my-button, my-table which are implemented by e.g. ng-semantic on web and hand coded for NativeScript but they have the same data contract and therefore other vertical cross platform feature modules can import them consistently on both platforms. I can only think of that build time solution to support AOT compilation.

Same approach is used by this seed project https://github.com/TeamMaestro/angular-native-seed

Do you have any plans to support this scenario? Pottentially be able to generate shared module using cli?

[m-abs]

I don't think that would fit very well with the way nx works.

Nathan posted a suggestion on the angular-seed-advanced project, that I think would be more fitting:
NathanWalker/angular-seed-advanced#474

[VladimirMakaev]

I see.. Basically that basically leeds to a desing like that:

Which might be just ok. Thanks for pointing me out to that issue.