Legend of ngModules - Angular 2 and Beyond
summary
One root NgModule boots every Angular app, modules group components directives pipes and services, and Angular CLI generates the boilerplate; declarations vs providers matters because declarations are for the compiler and providers feed the app injector. Submodules must exported declarations only to be visible when imported. Lazy loading a feature module can cut initial load from several seconds to about 400ms in the demo. Never avoid providing services in lazy/shared modules if a single instance is required to prevent duplicate injectors.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:29Why this talk
- 1:52Who am I
- 4:37Legend of ng Modules
- 5:35ES6 Models
- 6:17Grouping ngModules
- 13:46Feature Functionality
- 15:00Clean Code
- 16:41Subdivide
- 17:17Import
- 18:15Imports
- 18:43App Model
- 19:24Logging Model
- 20:29Login Model
- 21:47Provider Pool
- 23:48Lazy Loading
- 25:06How does it work
- 26:46Whats next
- 27:03Shared Models
- 27:23Core Models
- 29:51Summary
related talks
22mModule vs Module
18mStandalone Components: The Motivation
34mImproving Start-up Performance with Lazy Loading in Angular 2
18mStandalone Components The Motivation
32mImproving Startup Performance with Lazy Loading in Angular
18mModules are not what you think they are
18mAngular's Future w/out NgModules Architectures w/Standalone Components
45mLazy Loading: Supercharge your Angular apps!