Hello, We have a custom app that has many modules, to enable re-usability and avoid deployment dependencies , we want to extract few modules and create a different application and move it private app store. But the question is, when we import modules in the main app, it becomes a local copy instead of a reference. Do we have an option importing to refer a module vs importing . The reason we would want to do this is , if we change the module on app store we want changes to be reflected in all other applications where referenced module is used. Thanks.
The advantage of being a local copy is that you will need to manually import the next version of your appstore app. Thereby browsing the release notes and executing a regression test. This becomes less important in your situation where you are yourself the creator of the appstore-app.
If your application is not dependent on your appstore modules, it has no direct reads or writes to it but just calls some microflows, then you can consider to setup your appstore module as a service. Create an application specifically for the apstore module and expose the functions of your appstore module as published services.