"Standalone" APIs: A Component-focused Angular
summary
Angular v14 introduces Standalone: true components that remove the need to create NgModules by putting dependencies into an explicit imports array, and lets routes use loadComponent dynamic imports for per-component lazy loading. Router gains provideRouter and routes gain a providers field so DI and lazy route trees work without module scaffolding. Existing NgModule libraries remain compatible; tooling (CLI, language service) adds auto-import fixes and scaffolding support as the APIs stabilize toward v15.
AI-written summary · about
chapters (11)
- 0:00Standalone Angular APIs intro
- 1:11Why Angular made Standalone APIs
- 9:04Problems with NgModules
- 11:54Standalone components
- 13:40Interoperability with libraries
- 16:12New use cases unlocked
- 19:42Simplifying APIs without NgModules
- 23:01Structuring apps without NgModules
- 26:13Future plans for Standalone APIs
- 28:44Tooling improvements
- 34:02Wrap-up and discussion
related talks
18mStandalone Components The Motivation
18mStandalone Components: The Motivation
18mAngular's Future w/out NgModules Architectures w/Standalone Components
32mLightweight Architectures with Angular's Latest Innovations
36mThe Era Of Standalone Apis
17mComponent-First Architecture with Angular Standalone Components
20mAngular Without the Framework: Standalone, Signals and Functional APIs
29mHow Well Do You Know Angular? Let's Have Fun Together!
