Honey, I shrunk your Ember app
summary
Shows how an Ember app shrinks by auditing the build pipeline with an bundle analyzer, finding duplicated libs and large imports, and applying lazy-loading components and a feature blacklist to stop accidental includes. Uses Ember CLI hooks and build-time checks to strip unused modules and enforce size budgets. Result cuts initial JS payload by tens to hundreds of kilobytes, fixes failing production bundles, and prevents regressions in CI.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:52THE FUTURE
- 16:52CUT DOWN ON ADDONS
- 20:06MANUAL DEAD CODE ELIMINATION
- 26:01KNOW YOUR TARGETS
- 31:54THE END OF OUR JOURNEY
related talks
28mFast-Track Ember with Fastboot + Embroider
45mHas Your App Slimmed Down for Summer?
32mLet's Tree-shake it...
38mWhat to do when your bundle needs to go on a diet
58m10KB or Bust: The Delicate Power of Webpack and Babel
28mDebugging the Performance of 4,860 Angular Apps
52m10KB or Bust: The Delicate Power of Webpack and Babel
42mHoney, I shrunk the node_modules!