Signals & Modern Angular
Angular Standalone Migration Guide
Migrating an NgModule application to standalone components is done incrementally with the official schematics. Angular ships three migrations that run in order and handle most of the mechanical work.
What is Standalone Migration Guide in Angular?
Migrating an NgModule application to standalone components is done incrementally with the official schematics. Angular ships three migrations that run in order and handle most of the mechanical work.
Standalone Migration Guide example
Terminal
ng generate @angular/core:standalone # run three times, choosing in order:
# 1. Convert all components, directives and pipes to standalone
# 2. Remove unnecessary NgModule classes
# 3. Bootstrap the application using standalone APIs
ng generate @angular/core:control-flow # *ngIf/*ngFor -> @if/@forKey points to remember
- Run each step, build, run tests and commit before moving to the next.
- Providers move from NgModule to app.config.ts or to route-level providers.
- Standalone and NgModule components interoperate, so the migration can pause safely.
- Migrate control flow syntax separately from the standalone conversion.
Common mistakes with Standalone Migration Guide
- Running all three steps in one commit, which makes any regression impossible to bisect.
- Forgetting that services provided in a removed NgModule need a new home.
Angular Standalone Migration Guide— Interview Questions & FAQs
Do I have to migrate to standalone components?+
No — NgModules still work. But new Angular features and documentation assume standalone, and the automated schematics make the migration largely mechanical, so most teams do it eventually.