Faster apps with Angular SSR
summary
Angular Server Side Rendering now reuses the DOM instead of destroying and re-rendering it, enabled by a one-line config change that triggers an annotation pass, serialization into the TransferState, and client-side DOM attachment. The system ships with built‑in HTTP cache transfer and an opt‑out attribute (NG_SKIP_HYDRATION) for incremental rollout. Developer preview targets v16, supports lazy routes, and reports up to 45% LCP improvement while paving the way for partial hydration and post‑hydration cleanup.
AI-written summary · about
chapters (12)
- 0:00Angular hydration intro
- 1:54What is hydration
- 2:36SSR before Angular 16
- 4:22Hydration reuses DOM
- 5:27Annotation and serialization
- 7:33Transfer state explained
- 9:58HTTP cache transfer
- 11:43Enabling hydration
- 13:49Hydration order and lazy routes
- 15:17Testing results
- 16:21Developer preview and plans
- 18:24Next steps
related talks
15mA journey to Server Side Rendering with Angular
19mSSR Faster with Angular & App Hosting
36mELI5 Angular Hydration
28mAccelerating Angular
41mServer-side rendering with Angular—be faster and more SEO, CDN and user-friendly!
41mRenaissance of Angular
21mStrategies for Server Side Rendering Angular Applications
24mAngular 2 Server Side Rendering