Components and Modules
summary
Panelists compare concrete tradeoffs: HTML Imports block by default but allow URL-traceable composition; ES6 modules give single-binding encapsulation and server/client isomorphic rendering but break static analysis and CSP tooling. Practical optimizations named are dependency tracing, server-side prefetch/vulcanize-style bundling, and HTTP/2 push to reduce RTTs; polyfilled Shadow DOM (Shady DOM) improves performance on old browsers. The conclusion: tooling and preprocessor pipelines get built around these primitives today, and setups either work now (with build steps) or degrade on legacy stacks.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:08Components
- 3:54Web Components
- 6:30React Components
- 8:08React Style Encapsulation
- 8:56Module Loader
- 10:45CSS Module
- 12:55Questions
- 19:28Content Negotiation
- 20:50Concerns
- 25:53Routing
- 28:13HTTP2 Concatenation
- 32:38Semantic Loss
- 34:05Audience Question
- 35:12Paul Irish
- 38:30Steve Souders
- 48:37Sebastian
- 54:03Robert Knight
related talks
27mThe future of frontend tooling
41mPanel: Web
33mES6 Modules in the Real World
19mMaking front end modules actually work
46mES Modules: The next revolution?
41mThe future is modules not frameworks. JS modules Architecture demo.
31mECMAScript Modules: Past, Present, and Future
34mBuild-time Optimizations in JavaScript Applications