-
Notifications
You must be signed in to change notification settings - Fork 0
Establish Monorepo Foundation & Shared Types Architecture #177
Copy link
Copy link
Labels
DevexDeveloper experience, local setup, and tooling improvementsDeveloper experience, local setup, and tooling improvementsGlobalChanges affecting the entire monorepo or multiple servicesChanges affecting the entire monorepo or multiple servicesImpact: HighSignificant user impact; immediate attention recommendedSignificant user impact; immediate attention recommendedInfrastructureCI/CD pipelines, cloud resources, Docker, or hostingCI/CD pipelines, cloud resources, Docker, or hostingPriority: HighUrgent focus required; blocks progress or major bugsUrgent focus required; blocks progress or major bugsTypeScript MigrationTasks for converting JavaScript code to TypeScriptTasks for converting JavaScript code to TypeScript
Metadata
Metadata
Assignees
Labels
DevexDeveloper experience, local setup, and tooling improvementsDeveloper experience, local setup, and tooling improvementsGlobalChanges affecting the entire monorepo or multiple servicesChanges affecting the entire monorepo or multiple servicesImpact: HighSignificant user impact; immediate attention recommendedSignificant user impact; immediate attention recommendedInfrastructureCI/CD pipelines, cloud resources, Docker, or hostingCI/CD pipelines, cloud resources, Docker, or hostingPriority: HighUrgent focus required; blocks progress or major bugsUrgent focus required; blocks progress or major bugsTypeScript MigrationTasks for converting JavaScript code to TypeScriptTasks for converting JavaScript code to TypeScript
Type
Projects
Status
In progress
Service / Component
Infrastructure /
services/sharedFunctional Area
Developer Experience / Type Safety
Problem
Without a centralized type registry, services across the monorepo are prone to "type drift" where interfaces for shared APIs (Discord, GitHub) or common UI patterns become out of sync. This increases the risk of runtime errors and violates our Layer 1 (Build Validation) strategy, which requires a unified foundation to catch errors at compile-time.
Proposed Solution
services/shared/types(@naur/types) workspace.package.jsonworkspaces.tsconfig.jsonpath mapping (@shared/types) for all services.Priority
High
Impact
High (Structural Foundation)