Optimise your Web Development Workflow
summary
Live demos show Chrome DevTools actually doing things: native Node.js debugging attached to a running process with breakpoints and live edit, an in-DevTools terminal that runs node, and a filesystem-backed workspaces 2.0 that writes files and triggers build tasks. Performance tools include per-line CPU profiling, FPS and paint profilers, and a new CSS coverage recorder that marks unused rules after arbitrary interactions. Several experimental features work during the talk and most demos succeed.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:24LAYOUT EDITOR
- 6:23CUBIC BEZIER EDITOR
- 7:21PERFORMANCE
- 8:50PAINT PROFILER
- 10:40LINE LEVEL PROFILING
- 12:24CONSOLE TIMING
- 13:04TIMELINE MARKING
- 15:11DEVELOPMENT WORKFLOW
- 20:01CUSTOMISING
- 23:27CONSOLE API
- 24:02REQUEST BLOCKING
related talks
20mGoing steady with the Chrome Dev Tools
20mJavaScript Authoring Tooling
49mEffective Browser JavaScript Debugging
37mAll tooled up and nowhere to go?
13mNew Chrome Dev Tool Functions that will blow your mind
28mGetting down to brass tacks: Using chrome dev tools to level up your applications
47mDebugging, Profiling, & Rocking Out with Browser-Based Developer Tools!
33mChrome DevTools, From Prototype to Production
