file-organization

Direct imports require referencing source files instead of intermediate index.ts re-exports. This practice improves tree-shaking and clarity, ensuring your file structure remains explicit and reducing refactor risk across your TypeScript codebase.

Place unit tests directly next to their corresponding source files to colocate them. This file organization strategy improves maintainability by keeping implementation and tests grouped together, reducing cognitive load during refactoring.

Use .js or .mjs extensions for your configuration and setup files to enforce ES Module formats. This standardizes ESM usage across your project, supporting direct imports and explicit type separation.

Yes, prefer import type for TypeScript type definitions to avoid inline mixed imports. This explicit type import practice separates types from runtime values, reducing bundle size and maintaining clean import patterns.

Documentation files should use kebab-case naming conventions for consistency. This standardizes file organization across your codebase, making documentation easier to locate and maintaining structural uniformity with descriptive filenames.

Standardize file structure during new component creation, refactors, or repository-wide reorganizations. Applying consistent file organization rules in these scenarios reduces cognitive load and improves long-term maintainability.