You Might Not Need a Build Step
summary
Argues that a full local build can be eliminated by using progressive bundling: request-time bundling in a cloud function (Rollup), fingerprinting via a SHA-1 hash, caching, then a 302 redirect to the hashed URL. Demonstrates live production usage on begin.com and CascadiaJS where an entry .mjs request returns a fingerprinted concatenated ES module bundle, proving bundling runs fast enough in a cloud function and users get cache-correct updates without a prepublish build step.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:35Motivation for skipping build steps
- 2:37What is a build step?
- 3:17Transpiling and its benefits
- 6:25Bundling and performance gains
- 7:26Caching and fingerprinting explained
- 10:17Modern web platform improvements
- 12:41Progressive bundling approach
- 16:15Live demo of progressive bundling
- 20:11Q&A session begins
- 20:54Tools for custom elements
- 21:56Caching on CDN and AWS
- 23:01Begin deployments and cloud functions
- 24:26Closing remarks and thanks
related talks
34mTowards a simpler JavaScript ecosystem
46mIn this JavaScript tooling jungle, a return to simplicity is...
15mBundling With H2 Server Push
30mExcuse Me, I Have to Assemble the Frontend
50mDo we really need this JAMstack thing? And what even is it?
33mNo-build: pipe dream, or near future?
17mBundling your Front-End with webpack
07mFrontend Application Bundles