angular-core

Signals provide reactive state management in Angular without class field mutations. Use signal(), computed(), and effect() to model state, and bind them directly in templates with zoneless change detection for optimal performance.

inject() keeps constructors lightweight and improves testability by retrieving dependencies at runtime rather than declaring them as parameters. It's the recommended approach for modern Angular patterns.

Zoneless change detection with provideZonelessChangeDetection() and OnPush reduces zone-related overhead and improves app performance by only detecting changes when signals emit new values.

No. Standalone components are the default in modern Angular. The decorator itself makes a component standalone without requiring the explicit standalone: true flag.

Use effect() to run side effects when signals change, eliminating the need for lifecycle hooks like ngOnInit. This keeps logic declarative and tied directly to state changes.

Yes. Native control flow syntax like @if, @for, and @switch is built into modern Angular templates, reducing boilerplate and improving readability without wrapper components.