React X Web Components: How it is and how it could be
summary
React currently forces awkward workarounds: props beyond strings serialize into object Object, events require manual wiring with useRef/useEffect, and libraries like Shoelace maintain separate React wrappers to stay ergonomic. The claim is that an experimental React branch already accepts arrays/objects and native custom events with predictable casing, demonstrated by a Vonage keypad web component wired both ways. The talk shows concrete code patterns, maintenance pain, and a viable path to remove the glue.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:21Web components matter
- 2:24Challenges in React today
- 3:27Experimental React support
- 5:54Community libraries
- 7:40Benefits of first-class support
- 8:23Cumbersome usage in React
- 9:25Simplified usage
- 10:52Future-proofing React
- 12:25Call to action
- 14:31Q&A
related talks
25mReact x Web Components : How It Is and How It Could Be
45mReact Web Components How It Is and How It Could Be
42mReact, Another Way to Think About Your Web Components
26mThe complementarity of React and Web Components
16mWeb Components Q&A
59mThe effect of React on web standards
20mI’m With Web Components and Web Components Are With Me
33mHow React changed everything