Hi,
@mehmet-erim I saw abp architectural style for angular modules, you defined sperate lib for each module and added them to your app-dev application, Is this style just for reusability of these libs in other application? should I create separate libs for each of my modules in Domain space? or only for my modules that share in other apps for reusability?
Each ABP modules are an NPM package. We created these modules as a library because Angular libraries can publish easily.
Should I create separate libs for each of my modules in Domain space?
Angular libraries are harder than standard modules to scale.
You can also create a module with ABP CLI. See https://docs.abp.io/en/abp/latest/Startup-Templates/Module
If you generate a module with ABP CLI, an Angular application with two libraries will be created. You must publish these Angular libraries to use in your main project.
If you don't need to reuse a module with different Angular projects, you should create a standard Angular module.
See the Bookstore tutorial to learn how to create a standard module and how to manage it.
thanks @mehmet-erim.
Most helpful comment
Each ABP modules are an NPM package. We created these modules as a library because Angular libraries can publish easily.
You can also create a module with ABP CLI. See https://docs.abp.io/en/abp/latest/Startup-Templates/Module
If you generate a module with ABP CLI, an Angular application with two libraries will be created. You must publish these Angular libraries to use in your main project.
If you don't need to reuse a module with different Angular projects, you should create a standard Angular module.
See the Bookstore tutorial to learn how to create a standard module and how to manage it.