Fellow reader Michael had a great question about yesterday's email β Why does this work!?
How does the Birthdays component use the return value from
useBirths
before the request is complete? Is it an empty array at first, and if so how?births.map
is called below, so we assume it's an array at the point of first render.
Here's the code again:
const Birthdays: FC<{ day: Date }> = ({ day }) => {
const births = useBirths(day)
return <Table data-testid="birthday-list">
<tbody>
{births.map((birth, index) => ( //...
</Table>
}
Why can we call births.map
and assume it's an array?
That's the clever trick behind React Suspense βΒ in JavaScript you can throw a promise.
You've seen throw new Error()
before. That lets you stop execution of your code when there's a problem and jump into the catch
block of a try/catch.
But you don't have to throw an error. You could throw a different object and give it special behavior in the catch block. That's what React does with Suspense β it catches unresolved promises thrown from your component tree then comes back to finish rendering when the promise resolves.
That means somewhere inside useSuspenseQuery
there will be code that throws your queryFn
. Let's see ...
Yep, here it is
// Handle suspense
if (shouldSuspend(defaultedOptions, result)) {
// Do the same thing as the effect right above because the effect won't run
// when we suspend but also, the component won't re-mount so our observer would
// be out of date.
throw fetchOptimistic(defaultedOptions, observer, errorResetBoundary)
}
If we're using suspense, throw the promise returned by fetch.
Brilliant π€©
~Swizec
Continue reading about Why useSuspenseQuery works
Semantically similar articles hand-picked by GPT-4
- Cleaner components with useSuspenseQuery
- React 18 and the future of async data
- Towards a Gatsby+Suspense proof-of-concept
- Async React with NextJS 13
- You can use React Query for slow computation, not just API
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below π
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails π on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. π"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help π swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers π ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are β€οΈ