You're listening to Syntax, the podcast with the tastiest web development treats out there.

Strap yourself in and get ready. Here is Scott Tillinski and West Boss.

Welcome to Syntax, the podcast with the tastiest web development treats.

Out there, we've got a good one for you today. We're going to talk about

moving from CJS, CommonJS, to ESM, ECMOScript modules. So this is a big transition that's

been happening in the node ecosystem for a while. I think it's at a point now where things are

starting to break if you're not in ESM. And I just moved over my entire platform. I'll talk

about it in a second. But I think it's a good time to talk about this and sort of go through it

because it's unfortunately not very easy to do this type of stuff. We're sponsored today by

Century. Century is the error and exception tracking platform. Actually, this is the perfect,

I got the perfect ad read for this one, Scott. So after I converted my entire application to ESM,

I tested it and everything, but you never know when you do the first deploy, especially when you are

changing the way that you run your application. So basically, I deployed that sucker,

and then I just sat there waiting for the sentry emails to come in or freshen the dashboard

for things to pop up. Luckily, only one minor thing had popped up, and I was very happy about that.

But it was very easy for me to quickly go in. I immediately made that into a GitHub issue,

and then it dumped all the information into the GitHub issue. I could go in, I fixed it,

and then in Century, you mark it as resolved, which basically is saying, get out of here,

and don't come back. I hope you don't come back. I hope you don't come back. It's really what it's

saying. Yeah. And what Century will do is it will say, okay, you fix this, and it will tell you,

in which commit you fix it to, or you can pin it to a specific version. And then if that same

issue comes back, it will tell you, hey, you said you fix it. You said you resolve this, but it's

...