Speaker Q & A
summary
No timeline is promised for a reactive forms overhaul but it’s acknowledged as the reactive forms top-voted issue; micro-frontends inside Google look like heavy lazy loading rather than separate apps; the router preload system has no preload retry or interceptor today; shared lazy bundles go into a commons chunk so shared code doesn’t download twice; entryComponents are now inert metadata and left in place until migration removes them (entryComponents left as metadata); upgrade roughly twice a year and try zero releases early.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:33Is There a Timeline for Giving Reactive Forms a Touch-Up or Overhaul
- 2:47Is There any Micro Front-End Apps in Google Build with Angular
- 7:35What Is the Best Way To Handle an Error When Fetching a Lazy Loaded Route Does There Does Preload Have a Retry or Interceptor
- 11:59How Do You Handle Shared Code
- 15:53Empty Constant
- 16:21Any News about Angular for Designers
- 16:41Ui Bakery
- 19:20Angular Photon
- 21:22Is There any Plan To Stop Support or Dab on Angular in the Near Future with So Many Frameworks
- 23:09What Can We Expect in Angular 10
- 26:23What Features Will Be in Angular 10
