Modularity Matters

on YouTube ↗19m

" summary

Explains concrete modularity choices for client JavaScript: use object literals, the module pattern and the revealing module pattern to get private state and controlled public APIs, add privileged getters/setters for extensibility, use a mediator (optionally with a facade) for loose coupling, and pick a packaging system — CommonJS (synchronous, Node/browserify), AMD (RequireJS) (asynchronous), or UMD for portability — with ES6 modules and transpilers like trencio and Square’s tool emerging as the future.

AI-written summary · about

" chapters (6)

1. 0:00Transitioning to web dev
2. 2:29Need for modular design
3. 3:54JavaScript module patterns
4. 9:44Decoupling with patterns
5. 10:43Module systems and formats
6. 15:58The future with ES6 modules

" related talks

• 29mA Brief History of ModularityAshley Williams · JSConf EU 2017
• 39mA brief history and mishistory of modularityAshley Williams · ffconf 2016
• 53mArchitecting Robust JavaScript ApplicationsTom Van Cutsem · JSConf Belgium 2020
• 41mThe future is modules not frameworks. JS modules Architecture demo.Brian Cavalier, John Hann · JSConf US 2011
• 40mScalable JavaScript architectureFrank Baele · Frontend United 2016
• 30mA brief history and mishistory of modularityAshley Williams · Nordic.js 2016
• 56mComponents and ModulesChristopher Chedeau, Christian Heilmann, Ian Feather, Guy Bedford, Alex Russell, Kaelig Deloumeau-Prigent · Edge Conference 2015
• 01h 10mModular JavaScript: Dynamic Dependency ResolutionYuriy Karadzhov · HolyJS 2020 Moscow