AMA with Igor Minar and Shmuela Jacobs
summary
Fix for lazy-loaded named router outlets in Angular 6 is confirmed and bugs can be triaged with a reproduction; Lighthouse and an axe-like accessibility tool fit CI checks; Google executes JS for indexing while other crawlers mostly do not and use short timeouts (roughly 5–10 seconds); Ivy aims to rewrite the renderer to enable code-splitting, tree-shake unused features, smaller generated code and easier debugging; use Angular Elements or iframes for runtime-plugged components and beware versioning and security.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:09Lazy loading Angular 6 modules
- 2:56SEO for SPAs
- 4:45Crawler detection of SPA load
- 6:31ngGirls introduction
- 7:54Angular v8 and Ivy goals
- 9:25Angular Ivy performance
- 11:56Angular vs React rendering
- 13:23Dynamic component loading
- 16:19Angular CLI vs Nx CLI
- 20:17Angular and Ivy future
- 23:30UI from JSON schema
- 25:17Closing
