June 2025: Talking Node, Next.js, and Error Handling

Unpacking server functions with Jack, Node 24 with Rafael, and a blog post to wrangle errors across your JS stack.

Hi friends,

It’s officially summer here in my half of the world, and the weather is reminding me daily that I live in the southeastern US: think hot temps, pop up rain showers, and lots and lots of humidity.

But I’ll take it: that’s what air conditioning and multiple showers in a day were made for.

In this month’s newsletter I cover:

• 2 podcast episodes with web developers Jack Herrington (who’s also my friend and co-host of our own podcast Front-end Fire) and Rafael Gonzaga.

• A blog post about effective error handling in JavaScript from the frontend to the backend.

Let’s get going.

---

I so enjoy getting to interview smart people doing cool things in web development on the LogRocket podcast. This month I interviewed my friend Jack Herrington, YouTuber extraordinaire and Node.js TSC member Rafael Gonzaga.

Imagine my delight when I learned I’d be interviewing my friend (and co-host of the Front-end Fire podcast) Jack Herrington on PodRocket.

Jack is super knowledgeable on all things web dev and puts out excellent YouTube videos to teach others, and he joined me to talk about one of his most recent videos discussing the truth behind server functions and how frameworks like Next.js and TanStack Start make them work even though they don’t exist in the web platform. If server functions continue to mystify you, this is a great episode to help clear up the confusion and tell you what you need to know to start using them today.

Likewise, Rafael Gonzaga, a Node.js TSC member, came on PodRocket to talk about cool new features dropping in Node.js 24. Some highlights include a new permission model, async local storage improvements, and V8 engine updates. There’s a whole lot of goodies worth checking out as well as some predictions for the future of the Node ecosystem, and well worth a listen.

---

Writing code means errors are bound to happen, since JavaScript can be written for the frontend or the backend, I blogged about how to handle errors at all levels of your tech stack.

JavaScript is a powerful coding language because it can run in the browser and on the server, but it also comes with plenty of its own unique quirks and pitfalls and errors.

Learning to gracefully handle those errors, whether they occur on the backend in a server application or the frontend in a client-side application, takes some practice and documentation reading, but if done well, really helps you debug issues much faster and lets users understand when something went wrong.

In this blog post, I cover how to throw errors on the server complete with HTTP codes and useful error messages and properly handle those errors on the client.

Trust me, after reading this, you’ll have a much better strategy for when your own app starts misbehaving, which it will, somehow, someday.

---

I hope you enjoyed this month’s edition of “Paige Codes.” Please share with your friends if you did.

See you again at the end of July,

- Paige

---

Not subscribed yet? No worries.

I send a free email every month or so. You can check out my archive, or sign up below: