How Many Ways to Say I'm Sorry, Error Handling in React
summary
Shows concrete claims and tools: using error boundaries (static getDerivedStateFromError vs componentDidCatch) plus try/catch, promise.catch, and type checking (Flow/TypeScript) to handle known, known‑unknown, and unknown errors. Demonstrates integration with GraphCMS, custom error types, and logging sinks like Sentry/Rollbar, plus live coding of broken fields and graceful fallback UIs. Claims that this approach cuts support load (fewer customer success tickets), captures context for debugging, and converts crashes into recoverable, user‑friendly states.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:12ERROR HANDLING = BETTER EXPERIENCE
- 5:09MORRIS ATTEMPTS TO MEASSURE THE SIZE OF THE INTERNET
- 6:10KNIGHT CAPITAL STOCK SOFTWARE BOUGHT HIGH AND SOLD LOW
- 7:31ERROR HANDLING IN REACT
- 8:48ERRORS ARE DEVIANCE FROM THE DESIRED GOAL
- 9:52What is an error in JSX?
- 11:57USE TYPE CHECKING
- 12:52CHECKING FOR UNDESIRED STATES
- 21:27REACT BOUNDARIES
- 23:39A CATCH IS AN OPPORTUNITY
related talks
48mProper Error Handling with React/Redux
32mError handling: doing it right!
08mEven Your Components Need a Safety Net: React Error Handling Deep Dive
28mError handling: doing it right!
32mWriting Better Errors
24mThrow Try/Catch in the 🗑️ Level up your React error handling with the Result type
13mError Boundaries Save You From Crashes! Here's How to Use It
32mPushing Bugs to Prod Responsibly with React and Redux