Modern Front End Routing
summary
Explains that the new App History API replaces pushState/replaceState with a single navigate(url, {replace, state, info}) that navigate returns a promise, exposes a navigate event with transitionWhile, transient state and an AbortSignal for fetch, and gives every history entry browser-generated id and key UUIDs plus history.goTo and updateCurrent. Prototype behavior works in Chromium now, promising simpler routing and micro‑frontend coordination, but wider browser support is not yet available.
AI-written summary · about
chapters (10)
- 0:00Introduction by host
- 1:48Speaker introduction
- 5:21History of client-side routing
- 9:15Limitations of the History API
- 12:04Introducing the App History API
- 18:44Key features of App History API
- 23:41Modern URL APIs
- 26:50Route matching challenges
- 29:20Future of routing APIs
- 30:23Closing remarks
related talks
41mThe future of routing with the Navigation API
17mModern Routing
14mThe HTML5 History API: PushState or bust!
29mHandle routes data using stateless protocol (using React Router)
01h 00mHow does a frontend router work? Deep dive with Vue Router
28mPast and future of client-side routing
33mPitfalls and Opportunities of Single Page Applications
28mStop Breaking the Web