Nx release secondary entrypoints sometime ago. By adding secondary entrypoints, we basically split our Angular libraries into multiple chunks, just like Angular Material does.
@manfredsteyer What do you think about using nx library-secondary-entry-point generator? the main library is the "domain" and the secondary entrypoints will be the "features", "ui", "utils", "api".
The structure be:
libs
+ booking
+ feature-search
+ src
+ lib
***.module.ts
- index.ts
- README.md
- package.json
+ feature-cancel
.... same as feature search ....
+ ui-search
.... same ....
+ src <--- this is the files and folders for the main library.
+ lib
+ applications
+ entities
+ infrastructure
- index.ts
- .eslintrc.json
- README.md
- ng-package.json
......
and the imports:
import { facade } from '@org/booking;
import { .... } from '@org/booking/feature-search';
...
example of creating library-secondary-entry-point:
Nx release secondary entrypoints sometime ago. By adding secondary entrypoints, we basically split our Angular libraries into multiple chunks, just like Angular Material does.
@manfredsteyer What do you think about using nx library-secondary-entry-point generator? the main library is the "domain" and the secondary entrypoints will be the "features", "ui", "utils", "api".
The structure be:
and the imports:
example of creating
library-secondary-entry-point
:What do you think?