Let me show you another error that can occur.

If you visit my profile endpoint at teamtreehouse.com/chalkers.json

we see a beautiful JSON file application, and we can work with this.

Well, what about if we go to another profile that doesn't exist, like

https://teamtreehouse.com/chalkers-not and hit Enter.

There's the text not found.

The text not found is not a valid JSON object.

Let's run the application with chalkers not as the username.

And this is the error that's displayed.

Our application is attempting to parse the string not found.

Not found isn't a valid JavaScript object.

That's why it say's unexpected token, meaning character n.

n is the first character it's trying to parse.

JSON files start with either an opening square bracket or curly braces.

Let's wrap the lines of code dealing with the parsing and

printing the message out with a try block.

Then we can catch the error and print it out.

Save the file.

And then rerun the application with an invalid username and

we don't get a stack trace anymore.

Once again, you can go ahead and include a more user-friendly message if you want.

Before we move on to the next error we handle,

since we're handling multiple errors, let's create a function that's

flexible enough to print out error messages from an error object.

Or any other object with a message property.

This means if we want to choose to implement how we handle errors differently

in the future, we only have to do it in one place.

Let's create a function PrintError.

That takes in one argument error.

And log out the error message.

Let's update where all the console.errors are with printError.

Awesome.