Angular Releases

Breaking Changes

• Standalone components promoted (not required, but encouraged)
• Router uses functional guards by default
• MDC-based Material components replace legacy Material

Migration Notes

The biggest change is Angular Material moving to MDC (Material Design Components). If you use Material heavily, test your styles. Standalone components are optional but worth adopting gradually.

Breaking Changes

• Required inputs (@Input({ required: true }))
• Signals introduced (developer preview)
• Server-side rendering improvements (non-destructive hydration)
• DestroyRef introduced as alternative to ngOnDestroy

Migration Notes

Mostly additive. Signals are preview only so no need to adopt yet. Required inputs catch template bugs at compile time. Run ng update and follow the schematics.

Breaking Changes

• New control flow syntax (@if, @for, @switch) replaces *ngIf/*ngFor
• Deferrable views (@defer) for lazy loading
• Signals become stable
• Standalone components become the default for ng generate
• View Transitions API support

Migration Notes

The new control flow syntax is a significant shift. Use the automated migration: ng generate @angular/core:control-flow-migration. Old syntax still works but will be removed in a future version. This is the version where signals become production-ready.

Breaking Changes

• Zoneless change detection (experimental)
• Material 3 design system by default
• Route redirects now accept functions
• New build system (esbuild + Vite) becomes default
• Fallback content for ng-content

Migration Notes

The new esbuild/Vite build system is significantly faster but may require adjustments if you relied on webpack-specific configs. Material 3 changes visual design. Zoneless is experimental but signals + zoneless is the direction Angular is heading.

Breaking Changes

• Standalone defaults everywhere (NgModules still work)
• Signal-based inputs/outputs/queries become stable
• Incremental hydration for SSR
• linkedSignal() for derived reactive state
• Resource API for async data loading

Migration Notes

Signal-based inputs replace @Input decorators for new code. Existing decorator-based code still works. The resource API changes how you load async data in components. Run the automated migrations first, then review signal adoption.