🏗️ Architecture: How should generated platforms achieve standalone compilatio...

Date: 2026-03-11
Time: 15:33:22 UTC
Session: gspace1-204.3
Agent: angular
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

How should generated platforms achieve standalone compilation without monorepo @libs-core/* dependencies?

Task: Not specified

🎯 Decision Made

Chosen:

Option A from S204 plan: generate local equivalents inline. Added replaceMonorepoImports() post-processor in module-generator.service.ts that replaces @libs-core/* and @libs-foundational/* imports with inline standalone equivalents. Also updated app-shell-generator to produce standalone package.json, angular.json, tsconfig, and environment files.

Options Considered:

• No alternatives documented

💭 Reasoning

Option A (inline equivalents) was chosen over Option B (SDK package) because: (1) Zero external dependencies — generated platforms are self-contained, (2) No package registry needed for standalone deployment, (3) Simpler CI/CD — just npm install && ng build, (4) The replaced libraries are thin wrappers (LoggerService = console, BaseEntity = interface, API_BASE_URL = InjectionToken), (5) Option B would require publishing/maintaining a separate @gograb/module-sdk package

📁 Files Involved

• libs/libs-ai/module-generator/src/lib/services/module-generator.service.ts
• APIs/backend-vitto-api/src/app/module-generation/generators/app-shell-generator.service.ts

🔗 Related

• Decision ID: dev_1773243202317_nacu3ii
• Session: 204
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation