Webpack in 5 Years?
summary
Webpack originates in 2012 and reaches ten years of maintenance, still growing on npm downloads, and claims core wins: code splitting on demand and co‑located assets plus server‑side bundling. Pain points are explicit: sprawling loader/plugin surface, GC pressure and single‑threaded JS hurting performance, and overwhelming initial config. Concrete proposals surface: versioned defaults or presets, a single plugin API exposing only used internals, opt‑in analytics to see real API usage, and making lazy defaults and incremental builds the baseline to scale large apps.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:06Background
- 1:46Webpack 10 Years
- 4:29Webpack Today
- 5:44Future Looks
- 7:05What can we do now
- 7:46Initial configuration
- 9:24Defaults
- 10:13Customization
- 12:06Analytics
- 13:10Performance
- 14:36What we should do
- 15:02Application size
- 15:50Incremental architecture
- 17:19Performance and architecture
- 17:55Summary
related talks
19mWebpack… and beyond?
29mWebpack 5 - Why Breaking Changes? What is next?
28mWebpack for a better development workflow
30mSnowpack, Webpack and the Third Age of JavaScript
11mJavascript Tooling - The Evolution and Future of JS & Front-end Build Tools
26mWebpack: Core Concepts and Advance Topics
31mWe Started Using Webpack and It Took A While
27mA re-introduction to webpack