Fix: How to systematically fix build errors for 9 libraries?

Documentation for Sessions

📝 Fix: How to systematically fix build errors for 9 libraries?

Date: 2026-01-27
Time: 16:36:10 UTC
Session: editor2-71.8
Agent: angular
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

How to systematically fix build errors for 9 libraries?

Task: Not specified

🎯 Decision Made

Chosen:

Fix root causes: 1. Switch ng-packagr to custom builder (ng-packagr has bugs), 2. Fix project.json path mismatches, 3. Add missing package.json files, 4. Move template logic to component methods, 5. Fix TypeScript strict errors individually.

Options Considered:

Fix each error individually as they appear
Identify patterns and fix root causes systematically

💭 Reasoning

Identified patterns: ng-packagr has recurring 'Cannot destructure property pos' bug → switch to custom builder. Many project.json files had wrong paths (libs-ui vs libs-ux, structural vs navigation) → fixed paths to match actual locations. Missing package.json → created minimal files. Complex Angular template expressions → moved to component methods. Result: 7 of 9 libraries fixed, 2 have remaining TypeScript code errors (ux-icons, ux-space).

📁 Files Involved

No files specified

🔗 Related

Decision ID: dev_1769531766533_pv5m2qo
Session: 71
Workspace: editor2

Auto-generated by MCP Smart Consolidation