Planning Migration to Strict Mode for Your Angular Apps
summary
A migration plan that turns a giant monorepo into incremental wins: use NX dependency graph to find bottom libraries, enable strictTemplates first to avoid breaking changes, then flip strict: true in many small PRs (target ~25 files each) while holding off on property-initialization and strict-null-inputs until later. Observability shows hundreds of thousands of template and type errors over two weeks, so shared libs and generators are migrated and editor strict mode is enabled to surface issues early, producing steady adoption across ~90+ projects.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 1:28Why migrate to strict mode
- 2:33Initial migration challenges
- 3:57Bottom-up dependency approach
- 5:25Three-phase migration strategy
- 6:30Enabling strict templates first
- 7:13Gradual flag enablement process
- 7:54Convincing management with data
- 8:56Migrating shared libraries
- 9:39Enforcing strict mode in editor
- 10:00Current migration status and next steps
related talks
35mHow to Organize an Angular Project
41mLong term success of your Angular projects
01h 00mUsing Monorepos for Scalable Apps
33mRefactoring 80+ Angular projects and what went wrong
44mRockin’ in the Angular World
22mClean Up Your Old Angular Apps!
42mRefactoring 80+ Angular projects and what went wrong
11mWhy I'm Excited About Angular for 2018 and 2038