angular-best-practices

Use ChangeDetectionStrategy.OnPush combined with Signals for state, and enable zoneless change detection in Angular v20+ via provideZonelessChangeDetection(). This eliminates zone.js overhead and triggers updates only when signal values actually change.

Lazy load feature routes with loadChildren or loadComponent, defer heavy components using @defer blocks, avoid barrel file re-exports that break tree-shaking, and dynamically import large third-party libraries like Chart.js only when needed.

Yes, Angular supports incremental hydration through provideClientHydration(withIncrementalHydration(), withEventReplay()). Combine it with @defer (hydrate on viewport) or (hydrate on interaction) to hydrate non-critical content lazily.

Frequent re-renders usually come from default change detection, methods called in templates, or subscribing to entire state objects. Switch to OnPush, replace template methods with pure pipes or computed() signals, and use fine-grained selectors.

Prefer Signals for synchronous component state and derived values via computed(), since they need no manual cleanup. Use toSignal() to bridge observables, and takeUntilDestroyed for remaining subscriptions to prevent memory leaks.