Vanilla Web: You Don't Need that Library
summary
A working vanilla e‑commerce demo is built with plain HTML, CSS and JavaScript, uses Web Components with Shadow DOM for isolated styling, client-side routing via the history API, a tiny reactive layer (Proxy/signals) for automatic UI updates, and is a PWA that installs and runs offline; the app has no build step, no dependencies, no node_modules, achieves high Lighthouse scores, and the implementation is published on GitHub and actually works.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:33A few questions
- 5:04How did we get here?
- 7:48Vanilla JavaScript
- 9:32Why you need to care about VanillaJS
- 11:22Advantages of VanillaJS
- 12:40Fears of VanillaJS
- 16:52Semantic HTML & Vanilla CSS
- 18:39Static generators
- 20:00Client-side routing
- 24:09Web components
- 26:32Custom element
- 28:32Template element
- 31:59Shadow DOM
- 34:22Reactive programming
- 37:03Web apps power
- 40:23Lessons
- 42:11Outro
related talks
01h 02mVanilla Web: You Don't Need that Library
30mVanilla JS: You Might Not Need that Library
22mThe vanilla way
51mWeb Components without Frameworks: Productivity, Speed & Independence
45mVanilla JS 2018
32mVanilla JS 2019
23mPros Do Vanilla - A Loosely Coupled Front-End
41mThe Future is Now: Web Apps Productivity without Frameworks#slideless.