Architecture: How to organize the growing number of module paths in tsconf...

Documentation for Sessions

🏗️ Architecture: How to organize the growing number of module paths in tsconf...

Date: 2026-01-16
Time: 22:05:40 UTC
Session: editor2-49.3
Agent: architecture
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How to organize the growing number of module paths in tsconfig.base.json?

Task: Organize tsconfig.base.json module paths into separate files by category

🎯 Decision Made

Chosen:

Split paths into category-based JSON files with merge script

Options Considered:

  1. Keep all paths in single tsconfig.base.json
  2. Use TypeScript project references
  3. Split paths into category-based JSON files with merge script
  4. Use NX path management

💭 Reasoning

Created a modular path organization system where module paths are stored in separate JSON files by category (restaurant, fitness, sports, retail, learning, culinary, dashboard, healthcare) under config/tsconfig-paths/modules/. A merge script combines these into tsconfig.base.json while preserving library paths. This approach: 1) Keeps tsconfig.base.json as the single source of truth for TypeScript, 2) Allows easy organization and maintenance of 147+ module paths, 3) Enables the vibe-universe platform builder to add paths to specific category files, 4) Provides validation and dry-run capabilities, 5) Maintains compatibility with existing NX tooling.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation