Error handling and retry with React Server Components
React Server Components can throw errors. Here's how to handle and recover from them
I'm an experienced full stack software engineer with a passion for UI.
I also love DIY, especially doing projects on my house.
import { ed } from 'England'
ed.improveWith('Natalia', 'Gandalf');
function EdSpencer() {
return (
<Engineer specialties={["Full Stack", "AI", "UX"]}>
<Languages
expert={["TypeScript", "JavaScript", "HTML", "CSS"]}
conversant={["Python", "C++"]}
/>
<Technologies
expert={["React", "Node", "Next.js", "Tailwind CSS"]}
conversant={["GraphQL", "PostgreSQL", "terraform", "Docker"]}
/>
<Experience
areas={["Cyber Security", "Frameworks"]}
management={true}
/>
<Embraces cicd={true} iac={true} />
</Engineer>
)
}
Stuff I've been working on lately
React Server Components can throw errors. Here's how to handle and recover from them
React Server Components let you send unresolved promises from server to client.
More than you ever need to know about how React Server Component Payloads work.
I've been writing JavaScript, HTML & CSS for 20 years. Along the way I've gotten good at UX, AI, IaC and CI/CD. My go-to's are TypeScript, React and Prisma, CICD'd to the cloud.
I've deployed large scale applications to AWS and Google Cloud, using terraform, kubernetes, and docker to create scalable architectures from the ground up using CI/CD and IaC.
I'm fluent with GitHub and GitLab CI/CD pipelines, and know how to get my code into production quickly and with high quality.
I've been programming with JavaScript since long before it was cool to do so. These days I'm a TypeScript fanboy, but I still love JavaScript. I'm also a big fan of React, Next.js, and Tailwind CSS.
I've also been written my fair share of Python, mostly using it for AI projects. I've used C++ for some embedded systems work, and hate Java. Well, dislike anyway.