js app. Honestly, handling errors is a very underrepresented topic in terms of educational content out there. And that's exactly what we found when this topic rose to the very top of a survey list that we did on our social media profiles. People were hungry to learn more about error handling, and with good reason.
This is an essential topic for any real-world view application. Errors are inevitable. We want to make sure that you know how to handle them. That's what this course is all about.
So what can you expect to learn? Well, number one, you'll learn how to handle errors in the context of view components, view composables, and even at the global view app level. We'll also dive into view specific error handling tools that come with the core view library out of the box. Things like the on error capture lifecycle hook and the global error handler that can be registered on the app config.
You'll also learn how to display error messages in line on your page directly within your view components or in a central hub. for alerts, in the case of many apps these days in the bottom right hand corner of the screen. Do note that this course builds off of our JavaScript error handling course. So if you haven't seen that course yet, we definitely recommend you start there.
It's going to start you out with the very basics, things like using try catch, catching errors in async code, but also goes through less technical concepts that are just as important to error handling, things like getting your messaging right for the end user and capturing your errors on a remote server with a service like Sentry, Bugsnag, or Rollbar so that your development team has full visibility into what's going wrong. If you haven't seen that course yet, go ahead and stop the video now, check it out, watch it, and then come right back here. In order to follow along with the code that I'm showing in the videos, you will have to download the boilerplate code from the project repository on GitHub. You'll notice that it is a Nuxt project.
Don't worry, all the concepts that we talk about in this course will also apply to a vanilla VGS project. I only used Nuxt just because I really enjoy some of the conveniences it provides. like the auto imports and the auto routing with the pages, the file based routing with the pages, and things like that. If there ever is a discrepancy between how things are done in Nuxt versus a regular view project, I will let you know about that.
Also, notice that you'll see TypeScript used a number of times throughout the boilerplate code. If you don't know TypeScript, don't worry about it. We'll walk you through those sections. or you can just ignore the TypeScript specific things and take the same exact concepts with you in vanilla JavaScript.
Now, for every lesson within the course, under the pages directory, there is a begin and end file. For example, in the next lesson, lesson two, you'll start by opening up to a begin. This is where the video starts. And by the end of the lesson, you can view to a end in order to see where the lesson ends up at the very end.
Now actually lesson two is a is a bit of a exception here because we kind of break that lesson up into two different begin and end files where we do just two different totally separate things in the middle of the video. But for the rest of the lessons you can check out the very first begin file with that lesson number on it. to follow along with the video and then see how things wind up at the end in the end file. For most of these lessons, to be honest, we are just walking through and talking through some of the code.
So a lot of the begin and end files look exactly the same. However, later on in the course, especially in the second chapter, we do start seeing more changes between the begin and the end file as we code along a little bit more together. All right. Ready to get started?
Download the boilerplate code, use the instructions in the readme to boot up your dev server, and in the next lesson, we'll start handling errors inside of view components.