Universally speaking

on YouTube ↗31m

" summary

Case study of moving a large Angular app (Trade Me) to server rendering: Node/Express server generated full HTML, CLI adds server module and serverTransition, and production system serves Universal pages with 682+ modules. Covers concrete fixes: avoid direct DOM by using the renderer and a windowRef/useWindow wrapper, prevent duplicate API calls with ngRx state transfer serialization into HTML, and trade-offs—slower TTFB, riskier TTI, extra build and monitoring complexity.

AI-written summary · about

" chapters (16)

1. 0:00Intro
2. 0:51This is a deep dive!
3. 3:07Goodbye AngularJS
4. 5:21Angular Universal
5. 6:27Performance
6. 9:41Facts about asteroids
7. 10:22Angular CLI
8. 15:51Four patterns
9. 16:30Avoiding the DOM
10. 17:02Components
11. 17:50Be explicit about it
12. 18:23Provide an alternative
13. 19:18Check the platform...
14. 21:09Just turn it off
15. 24:02State Transfer
16. 27:43Complexity

" related talks

• 26mServer Side Rendering with Angular UniversalNir Kaufman · AngularUP 2016
• 51mThe Jedi Path to Angular UniversalMichel Murabito · Angular Day 2018
• 42mUniversally SpeakingCraig Spence · ComponentsConf 2019
• 21mStrategies for Server Side Rendering Angular ApplicationsVikram Subramanian · NGConf 2018
• 28mServer-side rendering with Angular 2Wassim Chegham · NG Poland 2016
• 31mAngular Universal in the Real WorldCraig Spence · AngularUP 2019
• 20mSven van StraalenSven van Straalen · AngularNL 2019
• 41mServer-side rendering with Angular—be faster and more SEO, CDN and user-friendly!Maciej Treder · JavaScript fwdays'19