Intro to Webpack and Code-splitting for Phoenix
summary
Explains using web pack with Phoenix to do real code splitting: uses require.ensure and the CommonChunksPlugin to let webpack statically analyze dependencies and produce multiple bundles so the entry stays small. Shows a concrete example dropping a 280 KB bundle that can balloon into multiple megabytes and cites Instagram’s pre-webpack ~15 MB problem. Notes chunked assets cache correctly under Phoenix instead of being forced behind query-string versioning.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:55Branch vs Webpack
- 2:47Codesplitting
- 2:57Connectivity issues
- 3:45Webpack plugins
- 4:21Dependencies
- 4:48Rewards
- 4:59Synchronization
- 5:20Cache
- 6:01Summary
related talks
28mWebpack for a better development workflow
31mOptimizing bundle with WebPack and Code Splitting
30mWebpack – The React Parts
52m10KB or Bust: The Delicate Power of Webpack and Babel
58m10KB or Bust: The Delicate Power of Webpack and Babel
23mStreamline your code with webpack
38mLook Before You Import: A Webpack Survival Guide
26mWebpack: Core Concepts and Advance Topics