How manfredsteyer/big-repo works
This is an Nx/Angular demo workspace containing ten domain applications and repeated feature/domain libraries, rather than a documented business product. The visible workflow is Angular startup bootstrapping an app module that imports its domain’s feature modules. The tree also shows application facades, entities, and data services, but their runtime relationships were not sampled; those are represented as subsystem components without invented call flows. The graph uses domain1 as a representative slice; equivalent app and feature structures recur across the tree.
Main entry points: app.module.ts Domain app module · main.ts Angular startup · app.component.ts App component · nx-welcome.component.ts Welcome component
Components 10
Angular runtime
- Angular startup
apps/domain1/src/main.ts - Domain app module
apps/domain1/src/app/app.module.ts - App component
apps/domain1/src/app/app.component.ts - Welcome component
apps/domain1/src/app/nx-welcome.component.ts
Domain features
- Feature modules
libs/domain1/feature-feature1/src/lib/domain1-feature-feature1.module.ts - Feature components
libs/domain1/feature-feature1/src/lib/feature1.component.ts
Domain layers
- Application facades
libs/domain1/domain/src/lib/application/feature1.facade.ts - Domain entities
libs/domain1/domain/src/lib/entities/entity1.ts - Data services
libs/domain1/domain/src/lib/infrastructure/entity1.data.service.ts
Other components
- Browser user
Connections 5
- Angular startup → Domain app module: bootstraps
apps/domain1/src/main.ts - Domain app module → App component: bootstraps
apps/domain1/src/app/app.module.ts - Domain app module → Welcome component: declares
apps/domain1/src/app/app.module.ts - Domain app module → Feature modules: imports features
apps/domain1/src/app/app.module.ts - Browser user → Angular startup: opens app