type-project-organization

Type organization uses unified export syntax with export * from statements at both root and module levels, creating single index.ts entry points per layer. This standardizes how types flow through your project and eliminates scattered named exports that cause conflicts.

Centralize shared types and options in a common directory, then re-export them through module-level index.ts files using full export syntax. This prevents duplication, simplifies maintenance, and gives consumers one predictable import path.

Full export syntax using export * from avoids naming conflicts, reduces refactoring risk when types change, and enforces a consistent export surface across all modules. It makes the dependency graph clearer and easier to maintain at scale.

Yes. Replace scattered type exports with unified index.ts entry points at root and module levels, move shared types to a common directory, and enforce full re-export syntax. This refactoring reduces import paths and consolidates your export surface.

Use a common directory when types or options are referenced across multiple modules to prevent duplication and circular dependencies. Centralizing these in one location creates a single source of truth that all modules can safely import from.

Run typecheck and export-structure checks to validate that all modules follow full export syntax, use centralized index.ts entry points, and avoid duplicate or selective exports. These checks enforce the unified convention across your project.