Error Handling in Nuxt 3
summary
Shows a small online course app (state in localStorage) that deliberately throws "could not update" when marking a lesson complete, then isolates that failure with createError and a Nuxt Error Boundary so only the lesson pane disappears while an error slot shows details. Resetting sets the error value to null and restores the component; to avoid an infinite crash loop the demo uses navigateTo before reset. Also notes a fatal error option that renders a full‑page error.
AI-written summary · about
chapters (9)
- 0:00Error handling in Nuxt 3
- 1:54Client-side error importance
- 3:24Client-side errors demo
- 5:57Nuxt Error Boundary isolation
- 8:30Error slots and reset logic
- 12:31Avoiding infinite errors
- 16:29Server errors and overview
- 21:05Q&A: Full page vs boundaries
- 24:35Q&A: Error Boundary and Vue
related talks
33mError Handling in Nuxt 3
31mCommon Mistakes in Vue and Nuxt and How to Avoid Them
13mError Boundaries Save You From Crashes! Here's How to Use It
08mUnderstand the hard parts of Nuxt
02h 31mPractical NuxtJS
26mNuxt Server Components Crash Course
25mContent Loading That Isn't Broken
01mDevelopers' Mistakes with Nuxt – Daniel Roe