Monday! Monday! Monday! Open wide dev fans! Get ready! To stuff your face with

JavaScript CSS! Node modules! Barbecue tips! Get workflow! Break dancing! Soft skills!

Web development! The hastiest! The craziest! The tastiest! Web development

treats! Coming in hot! Here is Wes! Barakuda! Boss! And Scott!

Tiltoro Logo! Tolinsky! Welcome to syntax on this Monday hasty treat. We're going to be

talking about Async local storage in the Async context API in JavaScript. This is a

server-side JavaScript thing that allows you to basically have a context amongst your

player call stack for any given piece of information that you want to share in that

regard. So my name is Scott Tolinsky. I'm a developer from Denver. And with me,

as always, is Wes! Boss! Hey! I'm excited to talk about it. I have done a

little tick-tock on it a couple of weeks ago and then I talked about it in my react

to thon talk, which was on like next gen JavaScript frameworks. Async local

storage is pretty cool. So we're going to kind of run through what it is and why

you might need it. Should we get on into it? We should. And I will be taking the role

of somebody who has not used it. I generally know what it is. But I will be trying to

ask you some questions. So if my questions seem dumb or if they seem like

off-based, try to steer me in that direction because I'm interested in this stuff. And I

kind of have an idea of when you would use it. But I want to really get the full picture

here. So Async local storage, my understanding is that this is a new API within

JavaScript inside of nodes specifically as well as what these other run times,

other JavaScript run times. When did this drop in node and is it like are all these

JavaScript run times aligned on this? So this dropped in node 13. So it meaning

...