Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
- ABP Framework version: v4.2
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:
The documentation at https://docs.abp.io/en/abp/latest/PlugIn-Modules does a decent job of explaining how to work with modules to separate new features on your main application, however all of the examples are for MVC. Is this possible for the angular UI as well? In mvc it seems you just add a new module and add your views, compile and include that somewhere so its loaded up by the main app, would there be a similar process supported for Angular? If not, does that mean that all of the features would have to be implemented for every deployment then since we cant split out module UIs?
2 Answer(s)
-
0
Hi @rcalv002
There are several module separation methods for Angular:
- You can split Angular modules into JavaScript chunks by applying the lazy-loading modules.
- You can create an Angular library for a module to separate the module and app folder. Thus you can convert your Angular solution to monorepo.
- You can create another Angular app, put your module here, publish the module to the NPM (or a custom NPM server), and you can implement the published module to your real app.
Although there are some methods for module separation, there is no method as described in the Plugin-Modules document.
-
0
This question has been automatically marked as stale because it has not had recent activity.
