Is a <Suspense /> boundary optional on suspense-enabled queries in @urql/next?

[kcrwfrd]

The documentation for using the client-side UrqlProvider in Next.js only includes an example with <Suspense />

However, I was surprised to find that when I removed the <Suspense /> it continued to work. Instead of rendering a suspense fallback and (presumably) streaming in the response, it seemed to block on the request to complete SSR.

I could test this by disabling JavaScript on the client side and loading the page. The successfully queried content could be seen rendered in the initial HTML payload.

This seems to behave the same as what's documented for React Query's useSuspenseQuery implementation:

If you call useSuspenseQuery without wrapping it in a boundary, the HTML response won't start until the fetch resolves. This can be what you want depending on the situation, but keep in mind that this will hurt your TTFB.

Is this correct intentional behavior in urql? Because in our case it is actually desirable due to SEO concerns.