Proper Error Handling with React/Redux
summary
Production bugs cause endless spinners and lost dinner time so the team accepts failures and builds tooling: global window.onerror plus source maps and stacktrace.js to get real files, a webpack first-entry for the handler, Sentry for collection, and action/reducer/saga wrappers — a safe bindActionCreators, redux-catch middleware, and a HOC called react-poop that replaces crashed components and logs state. The system captures component name, props, action type and state so faults reproduce and fix faster.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:34Let's talk about errors
- 7:43Requirements
- 10:49Common error handling solutions
- 28:43Components
related talks
32mPushing Bugs to Prod Responsibly with React and Redux
08mEven Your Components Need a Safety Net: React Error Handling Deep Dive
25mReact developer? How are your production skills?
31mHow Many Ways to Say I'm Sorry, Error Handling in React
12mSolve 100% of your errors
27mHow to Write Bad Code in Redux
22mCrafting Pristine React: Best Practices for Maintainable Code
08mTrack Slowdowns and Crashes in your React apps