Building Fast Angular Applications by Default
summary
Concrete results and tools: Ivy enables smaller, tree‑shakable runtime code and dynamic imports for component‑level code‑splitting; differential loading cuts about 40 KB from polyfills and ~-7% per bundle by serving ES2015 to modern browsers; bundle budgets fail CI when size regresses; progressive rehydration (progressive bootstrapping) lets the page stay interactive by downloading only the component JS on first interaction reducing initial JS from ~200 KB to ~20 KB; predictive prefetching (Quicklink / Guess.js) and ng deploy complete the pipeline.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:28Network Performance
- 2:25Lazy Loading
- 4:18Differential Loading
- 4:52Faster Execution
- 5:34How Differential Loading Works
- 6:08Differential Serving
- 8:18Browser First-Class Support of Differential Script Tags
- 10:50Component Level Code Splitting
- 11:04Support Widget
- 22:00Prefetching
- 23:07Predictive Prefetching
- 24:44Predicted Prefetching
- 29:16Ng Deploy
- 33:59Is It Possible To Display some Progress Bar while You'Re Loading Your Model
- 34:59Lazy Loaded Models
- 36:10Server-Side Rendering
- 38:31Progressive Refrigeration
- 39:39Progressive Bootstrapping
- 40:45Faster Rendering
- 43:13We Took a Look at Reducing the Bundle Sizes We Discuss How We Can Speed Up the User Navigation by Using Techniques Such as Prefetching It Could Be either Doing some Data Data Analytics for Example Guess Jess or It Can Just Take a Look at All the Visible Links on the Page and Preload the Content Associated with Them We Looked at the Upcoming Automated Deployment to Different Cloud Providers We Discussed Progressive Rehydration Which Will Allow the Bundle Size To Drop Dramatically and We Talked about Compile Time Optimizations by Using Ng C & Ng Tc Which Is Coming with Id so this Is the Last Question
