Dependency Injection for Future Generations
summary
Argues that Angular 2’s DI replaces Angular 1 pain points with a binding-based injector that is framework‑agnostic, supports synchronous and asynchronous creation via resolveAndCreate and toAsyncFactory, reads ES7 decorator metadata emitted by Babel or TypeScript, and uses child injectors for non-singleton instances. Shows concrete code: bind token→class/value/factory, promises returned for async factories, and injectPromise/injectLazy decorators to consume them. Demonstrations compile to ES5 and interoperate with existing module loaders, and the prototype‑style child/parent injector lookup actually works in practice.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:30Pascals latest achievements
- 2:25What are you talking about
- 3:10Dependency Injection
- 10:30Problems
- 22:48Asynchronicity
- 30:48Questions
related talks
57mAngular Dependency Injection, In Depth
23mDependency Injection in Nest and Angular: Intersection & Mismatch
46mAngular Dependency Injection – Understanding hierarchical injectors
01h 00mAngular Dependency Injection In-Depth
17mDissecting Dependency Injection: Angular and NestJS
29mDI Deep Dive
39mDeep DI-ving: how Angular's DI system defeated a monolith
27mDemystifying Dependency Injection: Angular vs NestJS