🏗️ Architecture: Should we temporarily disable strict mode for libraries with...

Date: 2026-01-25
Time: 15:25:28 UTC
Session: editor2-70.6
Agent: architecture
Confidence: 80%
Status: ✅ Documented

📋 Decision Context

Question:

Should we temporarily disable strict mode for libraries with type errors, or fix all errors now?

Task: Handle TypeScript strict mode errors uncovered by fixed build system

🎯 Decision Made

Chosen:

Document the errors and provide user with options: 1) Fix all 60+ type errors now, 2) Temporarily disable strict mode for affected libraries, 3) Use non-strict build temporarily

Options Considered:

1. Fix all 60+ type errors immediately
2. Temporarily disable strict mode for affected libraries
3. Revert build script changes
4. Create separate strict/non-strict build configs

💭 Reasoning

After fixing the build script to properly inherit parent tsconfig options (including strict: true), we uncovered 60+ legitimate type safety issues across 8 libraries. These are real bugs where code assumes values are non-null without checking. However, fixing all of them immediately would take significant time. Options: 1) Fix now (blocks delivery but ensures type safety), 2) Temporarily add 'strict: false' to affected libraries' tsconfig.json (unblocks build, creates technical debt to fix later), 3) Keep strict mode and fix incrementally per library. Recommending option 2 for pragmatic approach - get build working now, track technical debt for later.

📁 Files Involved

• libs/libs-ux/ux-menu/**/*.ts
• libs/libs-ux/ux-utils-lib/**/*.ts
• libs/libs-widgets/**/*.ts

🔗 Related

• Decision ID: dev_1769354728868_9rtuf07
• Session: 70
• Workspace: editor2

Auto-generated by MCP Smart Consolidation