Pushing Bugs to Prod Responsibly with React and Redux
summary
Claim: accept that bugs happen and focus on recovering fast. Shows concrete instrumentation: a Redux middleware that wraps dispatch in try/catch, captures error.name/message, the action and optionally log the whole state, and forwards payloads to an exception tracker. Recommends real tools (Airbrake is used) and demos a working redux-airbrake integration that yields readable backtraces, environment/browser context and alerts; example analytics report shows 645 reference errors, so teams know where to fix first.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:55Welcome
- 2:20Todays topic
- 3:00The Analytical Machine
- 3:48The First Programmable Computer
- 4:16The Birth of JavaScript
- 5:39Reference Error
- 11:50Capturing Exceptions
- 12:26Errors
- 15:25Resource Road
- 16:52Middle Work
- 23:31Exception Tracking Tools
- 26:37Open Source Exception Tracking
- 29:30Redux Tab
related talks
48mProper Error Handling with React/Redux
30mHow to push a ReactJS application in production...
25mReact developer? How are your production skills?
20mDebugging flux applications in production
12mReducing bugs in a React codebase
26mTime travel debugging: A step-by-step guide
35mDebugging JS and React
22mCrafting Pristine React: Best Practices for Maintainable Code