Multiple useSWR Hooks With Suspense Triggers a Hooks Order Warning

SWR does not support calling useSWR more than once per component under any configuration.

When the first useSWR call suspends on its initial fetch, the component throws a promise before the second useSWR call is ever evaluated on that render; the render that resumes after data arrives executes a different sequence of hook calls than the render that suspended, violating React's fixed hook-count-per-render requirement.

Because both calls share the same fetcher reference, SWR's internal cache collapses them into a single hook automatically.

Suspense boundaries require every hook inside the wrapped component to be declared through useMemo rather than called directly.