Modern Web Debugging
summary
Chrome DevTools shows what actually maps to authored files so stack traces and breakpoints point to your components rather than framework code and compiled bundles; features include hide framework frames, group by authored and deployed and a manual add-to-acknowledge for React. Breakpoint UX now groups by file and supports quick conditional and log-style breakpoints via command-click conditional/lockpoint. DevTools also supports overriding response headers, saving JavaScript snippets, and an “emulate focus” mode; source‑map spec limitations and how build tools must opt in are covered.
AI-written summary · about
chapters (16)
- 0:00Modern web debugging
- 1:13Web dev evolution
- 3:18Stack traces with framework hiding
- 6:05View authored code
- 7:50Source maps explained
- 10:18Ignoring files in React
- 12:49Breakpoint improvements
- 14:36Breakpoint types in DevTools
- 17:23Source map challenges
- 19:52Standardizing source maps
- 20:14Tailwind CSS tips
- 21:20Override HTTP headers
- 23:27JavaScript snippets
- 24:55Emulate page focus
- 26:00Run commands efficiently
- 27:02Report DevTools bugs
related talks
50mModern Web Debugging
43mModern web debugging with devtools
42mDebugging & DevTools
28mDevTools for the Progressive Web
27mChrome DevTools: State of the Union 2024 - Debugging React & Beyond
35mOptimise your Web Development Workflow
33mEssential JavaScript debugging tools for the modern detective
37mAll tooled up and nowhere to go?
