Shu Ding

It seems that you are using a custom cache, did you follow the migration guide here in the "Internal structure of the cached data" section? https://github.com/vercel/swr/releases/tag/2.0.0-beta.0

Yeah the new versions have been refactored to support better concurrent rendering scenarios, meanwhile it's possible to cause some misbehaviors. We currently can't reproduce the described problem, and something like...

If you are not using Suspense, it will likely not to be the cause. That said, v2 **should** work fine with Suspense and/or React 17, so this is definitely a...

Thanks for the detailed description! So the solution would be something similar to the impl. of useSWRInfinite, but requests are fired together instead of paginated. Happy to add it if...

> desired semantics of this hook aren't necessarily clear Agreed here @mAAdhaTTah, I think the most important thing to do first is getting a RFC/proposal instead of jumping into the...

Thanks for creating this! Still there're a few things about clarification when using Suspense in SWR (or any other data fetching library). I personally still don't recommend using it in...

Sorry I didn't mean that data fetching libraries should not use Suspense. What I'm thinking is Suspense based data fetching is almost impossible to implement correctly in the library level...

👋 Hey! I answered @pkellner's question [here](https://github.com/vercel/swr/issues/1906#issuecomment-1094416833), as I said: > I will keep this issue open until we add more clarification and guidance on Suspense and SSR to the...

Thanks for opening this! By definition `onSuccess` and `onError` are only called with actual requests, because there’re just too many deduplicated revalidations, so these give the “global” events. But there’s...

I realized that I misunderstood your original message and it’s indeed a problem. Will figure out a way to fix it!