Standalone components Angular
Why did Angular move to standalone components by default, and how do you migrate an NgModule app?
Answers use simple, clear English.
Audio N/AQuick interview answer
Standalone components declare their own imports, simplifying mental model and lazy boundaries — NgModules become optional. Migrate feature-by-feature with schematics: convert declarations to standalone: true, move imports to the component, update routes to loadComponent, then shrink NgModules until removable.
Detailed answer
Standalone components declare their own imports, simplifying mental model and lazy boundaries — NgModules become optional. Migrate feature-by-feature with schematics: convert declarations to standalone: true, move imports to the component, update routes to loadComponent, then shrink NgModules until removable.
Real example & use case
Lazy route loadComponent: () => import('./users.page').then(m => m.UsersPage).
Pros & cons
Pros: simpler DI/template imports. Cons: large apps need incremental migration.