The Era Of Standalone Apis
summary
Claims that Angular v17 restores component-only bootstrapping using a standalone property and new CLI behavior, shows concrete commands like ng generate component/ng generate guard and functional APIs (CanActivateFn, ResolveFn, HttpInterceptorFn) with inject for DI, explains project files app.config.ts and app.routes.ts including loadComponent/loadChildren, demonstrates migration schematic to convert components and remove NgModules, and cites a reported ~32% performance win for large apps while describing how to wire third‑party modules via importProvidersFrom and provideHttpClient with interceptors.
AI-written summary · about
chapters (14)
- 0:00Standalone APIs in Angular
- 7:26Modules to Standalone components
- 11:15Standalone artifacts with CLI
- 15:11Functional APIs for guards etc.
- 19:13Providers in Standalone apps
- 22:22Library support Standalone vs modules
- 24:31Migrating to Standalone
- 25:33Standalone future and takeaways
- 27:00Q&A: Dependency injection
- 29:50Q&A: forChild in Standalone
- 30:56Q&A: Standalone vs modules
- 33:04Q&A: Performance benefits
- 33:46Q&A: Standalone and micro frontends
- 34:09Q&A: Bundle size
related talks
18mStandalone Components: The Motivation
18mStandalone Components The Motivation
32mLightweight Architectures with Angular's Latest Innovations
51mThe Angular Renaissance - Key New Features
36m"Standalone" APIs: A Component-focused Angular
18mAngular's Future w/out NgModules Architectures w/Standalone Components
17mComponent-First Architecture with Angular Standalone Components
20mAngular Without the Framework: Standalone, Signals and Functional APIs
