Ad hoc data fetching with Suspense

[OliverJAsh]

.@aaronabramov suggested that I file an issue for this: https://twitter.com/dan_abramov/status/1522207779984793601

---

👋 I have a question about React 18 + Suspense. From the docs:

Ad hoc data fetching with Suspense is technically possible, but still not recommended as a general strategy.

When can I find more information about how to do this?

The reason I ask is because at Unsplash we have basically created our own routing / data fetching framework after running into too many limitations with existing solutions—so we'll need to figure out how to incorporate Suspense into our data fetching framework.

The best example I've found so far is this talk by Jared Palmer but I suspect it's outdated now?

[gaearon]

Does your framework allow refetching or cache invalidation?

[OliverJAsh]

No, once the data has been fetched, we never attempt to fetch it again—we re-use the cached result from the previous request (which we currently store in Redux).

[rajington]

Maybe there are open source frameworks that are on the right path? Or is data fetching in v18 itself still not ready for primetime? (also get if it's a tough question to answer and still early).

• swr experimentally supported suspense in v17 but v18 seems in progress
• urql and react-query seem to have some recent v18 fixes
• apollo is also working on it
• since @OliverJAsh uses redux, RTK seems to have something in progress too

I could do a codesandbox with all the different suspense implementations in v18, but I'm not sure if I'm familiar enough to test other than a single data fetch.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!