Lightning talk from Andrey Sitnik
summary
JavaScript libraries often hide big transitive costs: polyfills and unexpected dependencies inflate bundles by tens or hundreds of kilobytes. Measure the real cost by building a minimal webpack project, requiring the library, and taking the delta. Use size-limit as a guard, run CI checks and fail PRs that add bloat, and use the --why flag to invoke bundle analysis. Practical results include a ~25% reduction in shipped JS.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:40The rule of optimization
- 2:03Bundle size?
- 2:16Small example
- 2:47Bundle size vs. the real cost
- 3:26Main reason of heavy bundle
- 4:03Size Limit calculates library size
- 4:27Size Limit prevents regressions
- 5:07Size Limit reduced...
related talks
58m10KB or Bust: The Delicate Power of Webpack and Babel
26mWeb Performance in modern JavaScript world
41mHow we make Web Apps lightning fast at Microsoft!
52m10KB or Bust: The Delicate Power of Webpack and Babel
31m10KB or Bust" The Delicate Power of Webpack and Babel"
27mDrawing the line between 3rd party and handcrafted code
24mDrawing the line between 3rd party and custom code
40mBuilding a Platform: Webpack and the Future
