Solid pattern for the SSR hydration part. One thing on the Tab 1/Tab 2 example you open with though, does the invalidateQueries call in Tab 1's onSuccess actually reach Tab 2, or does Tab 2 only catch up once refetchOnWindowFocus fires because the user switches to it? If it's the latter, the multi-tab staleness problem isn't fully solved without something like a BroadcastChannel to trigger the invalidation cross-tab.
Tarun Sharma
React.js Frontend Web Developer | Next.js Specialist
Solid pattern for the SSR hydration part. One thing on the Tab 1/Tab 2 example you open with though, does the invalidateQueries call in Tab 1's onSuccess actually reach Tab 2, or does Tab 2 only catch up once refetchOnWindowFocus fires because the user switches to it? If it's the latter, the multi-tab staleness problem isn't fully solved without something like a BroadcastChannel to trigger the invalidation cross-tab.