Dependency Injection in Nest and Angular: Intersection & Mismatch
summary
Claim that Nest and Angular share an API but implement DI differently and prove it with concrete artifacts: the TypeScript emitted design:paramtypes metadata and the reflect-metadata polyfill, Angular’s extra compiler step and NG factory output, and Nest’s module-level injectors with explicit exports. Shows limitations with interfaces, generics and circular deps and the usual fixes like forwardRef or AST tooling. Notes a surprising 300% GitHub star growth and previews Nest adding request/transient scope provider lifetimes.
AI-written summary · about
chapters (8)
- 0:00Introduction to NestJS
- 2:12The concept of DI
- 3:29How DI works in runtime
- 6:54DI in Angular vs NestJS
- 8:26Challenges with DI
- 12:06Injector trees and isolation
- 16:40Future developments
- 20:34Closing discussion
related talks
17mDissecting Dependency Injection: Angular and NestJS
28mBeyond TypeScript Metadata: Dependency Injection in Angular and Nest
27mDemystifying Dependency Injection: Angular vs NestJS
57mAngular Dependency Injection, In Depth
38mDependency Injection for Future Generations
28mLeveraging Angular in Node.js with NestJS
01h 00mAngular Dependency Injection In-Depth
22mProductivity Revolution: Angular Principles in Node