Code Organization in Large Projects

In large projects, organization is key - just like in the shogun's army, everyone must know their place.

Barrel Exports (index.ts)

// features/samurai/index.ts
export * from './samurai.component';
export * from './samurai.service';
export * from './samurai.model';
export * from './components/samurai-card.component';

// Usage - one import instead of many
import {
  SamuraiComponent,
  SamuraiService,
  SamuraiCardComponent
} from './features/samurai';

Naming Conventions

feature.component.ts       # Component
feature.component.html     # Template
feature.component.scss     # Styles
feature.component.spec.ts  # Tests

feature.service.ts         # Service
feature.guard.ts           # Guard
feature.directive.ts       # Directive
feature.pipe.ts            # Pipe
feature.module.ts          # Module (legacy)
feature.routes.ts          # Routes (standalone)

Best Practices

1. One component = one directory (with related files)
2. Group by functionality, not by type
3. Use barrel exports for clean imports
4. Core for singletons, Shared for reusable elements
5. Lazy loading for feature modules
6. Maximum 400 lines per component file