Hasty Treat - React Suspense
In this Hasty Treat, Scott and Wes talk about React Suspense — what it is, how it works, support and more!
If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”.
Not live yet - it may/will change. Be warned!
3:59 - The problem we have with React right now
- API calls
- Image loading
- Code splitting
7:16 - What is React Suspense?
- First we convert our async data fetching functions into resources
- Resources can then be read inside render - above the return
- Resources can be read from cache
- Resources can be preloaded into a cache if you anticipate needing them
- Resources reads are blocking for that function - you can’t return JSX until the resource is read
- In your component that fetches data, there is no need to maintain a loading state
- Then, anywhere higher up in that tree, you can introduce a suspense component
- The suspense component can detect if any of it’s children are currently loading data
- If they are, we can then choose to show a loader via the fallback prop
- We can also choose to show nothing via the maxDelay prop — this is helpful for fast connections that shouldn’t see the spinner for a short split-second
15:20 - Support
- React.lazy and suspense for code splitting is already here
- The React.lazy function lets you render a dynamic import as a regular component
- Loadable Components is recommended if you need splitting with SSR
- Data Resources is not here yet