Hasty Treat - Async + Await Error Handling Strategies

Syntax - Tasty Web Development Treats

Wes Bos

Tech News, News, Technology

4.9 • 1.2K Ratings

🗓️ 6 May 2019

⏱️ 12 minutes

🔗️ Recording | iTunes | RSS

🧾️ Download transcript

Summary

In this Hasty Treat, Scott and Wes discuss different error handling strategies. Sentry - Sponsor If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”. Show Notes 2:07 - Try / Catch This can be done at call time or inside the function 4:10 - Higher Order Function Makes a function that returns a new function which in turn calls your original function (but with a .catch chained on) 7:46 - Handle the error when you call it Use async/await but chain a .catch onto the end 9:03 - Node.js Unhandled Rejection Event process.on('unhandledRejectionEvent', callback) 9:40 - What do do with those errors Send to error tracking service Possible to give the user a reference number Display good error text to user Tweet us your tasty treats! Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets

Transcript

Click on a timestamp to play from that location

0:00.0	Monday, Monday, Monday,
0:02.0	Open wide Dev fans.
0:04.0	Get ready to stuff your face
0:06.0	with JavaScript, CSS, node modules, barbecue tips,
0:09.0	get workflows,
0:10.0	break dancing, soft skills, web development,
0:12.0	the hastiest, the craziest, the craziest development the hastiest the craziest the tastiest web development treats coming in hot here is
0:18.1	Wes Barracuda bars and Scott El Toroloco, Tolinsky.
0:25.0	Welcome to Syntax in this Monday hasty treat.
0:29.0	We are going to be talking about a sink, or a sink, a weight and error handling strategies. My name is Scott Tulliskey. I'm a
0:36.4	full-stack dev from Denver, Colorado, and with me as always is West Boss.
0:40.3	Hey everybody, I'm excited to talk about error handling strategies.
0:44.0	Yeah, this is the most fun topic in the world.
0:47.0	The error handling strategies because we all love it when stuff goes wrong.
0:50.0	Talking about error handling strategies is going to be West with this week's sponsor is century
0:55.7	Actually this is not intentional, but Century is sponsoring today and part of our notes is what do you do with those errors once you've actually handled them or how do you handle them and one ways you can send them off to Century.
1:08.4	You don't actually have to send them to Century manually.
1:11.2	Century will just be installed to your server or to your
1:14.4	client side and it will sort of just listen for any errors that happen and then it will
1:18.6	collect as much information about what
1:25.0	information about what went wrong and compile that into a nice dashboard,
1:24.0	give you a thing like breadcrums, stack traces,
	...

Please login to see the full transcript.

Previous episode | Next episode

Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.