ES Modules: The next revolution?
summary
Native ES2015 modules land in modern browsers but prove not yet a drop‑in replacement for bundlers: experiments with a ToDo MVC and a modular lodash show many small files and 157 requests that slow cold loads, while bundles from WebPack and Rollup deliver fewer requests and faster start times. Native features like import() lazy-loading, modulepreload, and HTTP/2 server push reduce the gap, and service worker precaching plus incremental updates make modules promising for PWAs, but current browser caching and ecosystem gaps keep bundling practical today.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:56About me
- 2:41Previous revolutions
- 6:07ES Modules in the browser
- 8:00What makes modules different
- 14:29Instantiation
- 18:52Experiment
- 24:24Import function
- 25:33Async function
- 29:58HTTP2 Push
- 34:31Conclusions
- 37:44Whats next
- 39:59Progressive Web Apps
related talks
33mES6 Modules in the Real World
27mThe future of frontend tooling
35mBrowser Package Management
47mNative JavaScript Modules: import {Browsers, Node.js}; export {production};
16mUnbundling the Future Web Runtime
31mECMAScript Modules: Past, Present, and Future
01h 10mThe future of JavaScript modules: JS module blocks and native bundling
56mComponents and Modules