ts-02-implement

To enforce named exports and barrel exports in TypeScript modules, you need a convention guide that scaffolds index.ts entry points and prohibits default exports. This ensures modular reuse and predictable imports across your project's small-to-medium modules.

The best TypeScript patterns for refactoring code involve applying early returns, strict typing, and avoiding the 'any' type. Enforcing these conventions during module refactoring improves code safety and readability while maintaining predictable structural patterns.

To scaffold a new TypeScript feature with strict coding conventions, start by automating the creation of named exports and early return patterns. This approach aligns new modules with project standards, enforcing clean, predictable code quality from the beginning.

This TypeScript implementation approach is designed for small-to-medium modules, not large enterprise architectures. It enforces strict patterns like named exports and barrel exports to ensure clean, predictable code quality within appropriately scoped feature boundaries.

You should avoid default exports in TypeScript except for entry points to ensure consistent, predictable import names across modules. Restricting default exports enforces a standardized naming convention that improves code quality and maintainability.