Webpack+WebAssembly: Under the hood
summary
Explains how webpack’s internals actually change behavior: the tapable plugin system becomes a monomorphic hooks API with promises/async optimized for V8, the resolver and module factory flow (enhanced-resolve, Acorn parser, templates, chunks) remain but accept non-JS assets, and experimental WebAssembly as a first-class citizen plus loaders (example: Rust loader) let wasm import like modules. Also adds sideEffects: false pruning that shrinks examples such as lodash from 223kb→3kb, and describes how these changes work in practice.
AI-written summary · about
chapters (4)
related talks
55mUnderstanding webpack from inside out
50mwebpack and the Challenge of WebAssembly
14mMore WebAssembly in your JavaScript
14mWebAssembly becoming the biggest platform
16mWhy WebAssembly
44mWebAssembly: the browser is now a real virtual machine
46mWebAssembly (Digging a bit deeper)
33mWhat WebAssembly means for React