angular-portal-init-module

What problem does it solve?

Feature modules in an Angular portal require consistent wiring for routes, guards, interceptors, and module-scoped providers, but doing it manually is slow and error-prone.

Core Features & Use Cases

• Module-scoped configuration generation: Creates [module].configuration.ts, configurations/api.configuration.ts, and @NgModule-based providers so interceptors and tokens resolve at the right scope.
• Routing + security setup: Generates routes.ts with guards and lazy-loaded child entities without adding providers to lazy routes.
• Optional permission and upload configuration: Adds configurations/permission.configuration.ts and configurations/upload-file.configuration.ts only when the module confirms those needs, with keyed contracts to keep route and config aligned.
• UI reuse via base select: Produces components/base-select/base-select.component.ts and .html to support standard dropdown/search behavior across entities in the module.

Quick Start

Generate the Angular portal feature module configuration for module "catalog" with routes, guards, module-level API interceptors, and a shared base-select component.