🐛 Bugfix: Why was the Angular app crashing with 'No provider found for...

Date: 2026-01-22
Time: 03:29:52 UTC
Session: editor2-54.4
Agent: angular
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Why was the Angular app crashing with 'No provider found for ModuleGeneratorService'?

Task: Not specified

🎯 Decision Made

Chosen:

Export real service from services folder

Options Considered:

1. Export stub class from types file
2. Export real service from services folder
3. Create new provider in app.config

💭 Reasoning

The barrel file index.ts was exporting a stub class from types/module-generation.types.ts instead of the real Injectable service from services/module-generator.service.ts. The stub had no @Injectable() decorator and no providedIn: 'root', causing Angular DI to fail. Fixed by explicitly exporting the real ModuleGeneratorService and ModuleKnowledgeService from their service files.

📁 Files Involved

• libs/libs-ai/module-generator/src/index.ts
• libs/libs-ai/module-generator/src/lib/types/module-generation.types.ts
• libs/libs-ai/module-generator/src/lib/services/module-generator.service.ts

🔗 Related

• Decision ID: dev_1769052592164_tannxpp
• Session: 54
• Workspace: editor2

Auto-generated by MCP Smart Consolidation