Tracing Complex Frontend Processes

on YouTube ↗04m

" summary

A small Vue plugin records causal call chains and injects a proxy so code traces show what triggered each async request and why a state change happened. Demo handles a 409 remote-change by reading the server’s new count (900), applying the local +1 and ending with 901 after retry, all without touching business logic and with roughly five lines of integration. The tracer graphs methods automatically and follows recursive calls for deep debugging.

AI-written summary · about

" related talks

• 25mFollow The (Full)stack Trace: Understand Your App with Distributed TracingWill Klein · React Rally 2019
• 22mTracing is for Everyone, Not Just Backend Engineers. (How Tracing Could Help Front-e...Nina Stawski · Observability Practitioners Summit 2019
• 07mIdentify Issues and Prevent Slowdowns in your Vue.JS AppsSimon Zhong · Vue.js London Live 2021
• 20mThe (Full)stack Trace: Understand Your App with Distributed TracingWill Klein · JSConf US 2019
• 19mReactivity in Frontend JavaScript FrameworksEvan You · DotJS 2016
• 09mHow to interpret Vue ComponentsLukas Stracke · Vueconf.US 2022
• 26mThe Trouble with TracersThomas Watson · NodeConf.EU 2019
• 01h 00mHow does a frontend router work? Deep dive with Vue RouterEduardo San Martin Morote · HolyJS Piter 2019