This is a quick follow up post to my previous post Using TypeScript async/await to simplify your SharePoint Framework code.
Since publishing my previous post, some folks have asked how would the error handling work when using async/await in SharePoint Framework. So decided to make this short how-to post.
At first glance, it is really straightforward, you essentially have to wrap your code in a try..catch block and the typescript compiler does the rest.
But there is something interesting here. Under the hood, SharePoint Framework uses the fetch API to make http requests. MDN has some great info on the fetch API if you haven't seen it already: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API
What would be surprising for some (including me) is that the fetch API rejects the promise only when network errors occur. A "404 Not found" is considered as valid response and the Promise is resolved.
E.g. If you make a get request to a SharePoint list which does not exist, the fetch API (and the SharePoint Framework) will actually resolve your Promise.
A fetch() promise will reject with a TypeError when a network error is encountered, although this usually means permission issues or similar — a 404 does not constitute a network error, for example. An accurate check for a successful fetch() would include checking that the promise resolved, then checking that the Response.ok property has a value of true.
There has also been some discusson on this on the SharePoint Framewok GitHub repo:
This is why, in addition to a try..catch block, you have to also check the Response.ok property of the returned Response. Here is the basic code you need to handle errors when using async/await:
What you can also do is, since the fetch API returns promises, you can use chaining to detect if the Response.ok property is false. Have a look at this post: Handling Failed HTTP Responses With fetch()
Update 6th May 2017: Here is a slightly more complex example where I have built a service with a custom get method which also handles errors for you:
And here is how to consume the service from your SPFx webpart:
Here is the GitHub repository for the service if you are interested:
Hope you find this useful!