Closed as not planned
Closed as not planned
Description
Originally posted in this issue.
The same code can execute sequentially or concurrently depending on the performance of the react application and the device.
In a challenging performance situation, Suspense siblings initialize as a waterfall instead of concurrently.
React version: 19.1.0
Steps To Reproduce
Source Code Links: Two Different Suspense-using libraries
- Using @tanstack/react-query: codesandbox.io
- Using @apollo/client: codesandbox.io
Repro Steps:
- Open the app in a new tab (Example link for @tankstack/react-query)

- Open network tools and refresh the page
- Notice that the requests to dummyjson are made in parallel

- Visit the performance tab in chrome devtools and apply 20x slowdown

- Refresh the page
- Notice that the requests to dummyjson are made in sequence
