Error Handling in Vue

All of you have seen users do weird things with your application and running into strange scenarios - who can't relate to this?For this and many other reasons, the right way of error handling is important in you application. Join Michael and Alex on a discussion of the different ways one can handle errors in their application.That includes not always showing an error page, but also handling errors request-based or component-based!On that note, error messages and how to write decent ones that are helpful for the users are discussed, as well as how components like NuxtErrorBoundary work under the hoodEnjoy the episode! Chapters(00:00) - Welcome to DejaVue (01:22) - The good old error page (01:58) - Write good error messages! (03:11) - The Vue global error handler (05:07) - Server vs. Client Errors in Nuxt.js (08:34) - The vue:error hook (09:05) - Global error handling for $fetch and interceptors (11:10) - Throw unhandled errors in Prod with Vue 3.5? (13:07) - Component-level error handling (16:33) - NuxtErrorBoundary (18:01) - defineAsyncComponent (18:53) - Request-based error handling (21:45) - New default values in Nuxt 4 (23:30) - Error Tracking (26:33) - Actually handling the errors (28:54) - Wrapping up Links and ResourcesState of JS SurveySentryBugsnagRollbarMichael's talk on error handling in NuxtMichael's article on error handling in Nuxt*And another deep dive into Nuxt 3 error handling*DejaVue #E034 - Data Fetching in Vue and NuxtVue Issue regarding throwing errors in production (low level)VikeNuxtErrorBoundary component Source CodeofetchZodValibotNuxt 4 error and data will be undefined by defaultCreate abstractions for your headings and buttonsYour HostsAlexander LichterBlueSkyTwitterYouTubeTwitchWebsiteMichael ThiessenTwitterYouTubeWebsiteLinks marked with * are affiliate links. We get a small commission when you register for the service through our link. This helps us to keep the podcast running. We only include affiliate links for services mentioned in the episode or that we use ourselves.

There are no comments yet.

Please log in to write the first comment.