0
Challenge · 38Payments, Uploads & Email
Transactional email (Resend)
Emailused in ~65% of apps
Every job board sends mail: 'Your application was received', 'A recruiter viewed your profile', 'Reset your password'. Get it wrong and the interview signal flips negative fast — you blocked the HTTP response on a slow SMTP call, you built the HTML with string concatenation that XSS'd the candidate name into the subject, or you fired the email inside a Server Action that then threw, so the user saw an error but the email still went out. Transactional email is where 'did the side effect happen, and did it happen reliably?' gets tested.
Core idea. A transactional email is a one-to-one message triggered by an event in your app (signup, application submitted, status change). With Resend you send it via a single API call; with React Email you author the template as a React component so the same JSX you already know renders to email-safe HTML. The senior move is to NOT send inline in the request path — you enqueue the send to a durable queue (Inngest) so a flaky email provider can't fail your Server Action, and retries happen automatically.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
CRUD ↔ HTTP verb
POSTCreateGETReadPATCHUpdateDELETEDelete
local list (React state)2 items
#1Ship the feed
#2Review PRs
network — request / response
Add, edit, or delete an item. Watch the HTTP verb fire, then the local list update after the response.
Each mutation waits for the server's response, then updates the local list immutably (map / filter / spread) — no full refetch. Showing the change before the response is optimistic UI (#71).
↑ play a little first, then dig in