No framework frontends in practice - use the platform!
summary
Argues that modern JavaScript builds a scalable SPA without a framework by using WebComponents and ES6 modules plus tooling: Webpack, webpack-dev-server, Babel and html-loader. Implements a tiny router in ~20 lines of code, registers components with customElements.define, and loads posts via the built-in fetch API to JSONPlaceholder — the page renders and navigation works with history API fallback. Notes no automatic reactivity: use events or observedAttributes for updates.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:30Overview
- 2:36About Karol
- 3:08Agenda
- 3:52Frameworks
- 6:39Bad stuff
- 9:31Are we ready
- 10:15Components
- 11:39Libraries
- 12:01Compatibility
- 12:19Coding
- 17:00HTML
- 23:29Document Query Selector
- 31:12Routing
- 42:48Conclusion
related talks
44mJavaScript in 2017: You might (not) need a framework
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
51mDeconstructing Web frameworks for a more resilient code base
46mScaling Micro-Frontends with Custom Elements
41mLow-budget JavaScript: composable frontends that are fun and friendly
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
43mFrameworks and the Future of the Web Platform
34mFrameworkless Frontend Development