Debugging With JS Frameworks
summary
Demonstrates concrete fixes: uses the Replay time‑travel debugger plus Chrome/Firefox DevTools, React/Vue DevTools and Redux to reproduce and inspect bugs, not just theorize. Replays show a resize handler executed 95 hits where elementNewWidth drops to NaN because scaleX becomes negative Infinity after dividing by bounds.currentWidth = 0; adding a guard and commenting the root causes gets a fix merged the next day. Another bug shows missing panel logic when dispatching setViewMode in Redux; moving the panel decision into the action centralizes state and stops the layout break.
AI-written summary · about
chapters (11)
- 0:00Introduction to debugging
- 2:05Why debugging is hard
- 5:59Debugging a real-world bug
- 10:38Inspecting tools for debugging
- 14:29Evaluating tools for debugging
- 17:39Understanding application behavior
- 18:01Debugging frameworks like Vue
- 24:00Debugging framework internals
- 26:09Common JavaScript patterns
- 31:48Debugging React and Redux
- 37:28Why debugging matters
related talks
01h 08mSquashing JavaScript Bugs
37mTime Travel Debugging JavaScript Applications
58mSquashing JavaScript bugs
49mEffective Browser JavaScript Debugging
33mEssential JavaScript debugging tools for the modern detective
29mEssential JavaScript debugging tools for the modern detective
53mBeyond console.log
28mEssential JS debugging tools for the modern detective
