major(next): support Next 13 and React Server Components

[JoviDeCroock]

Resolves #3208
Resolves #3219

Summary

This creates a new package @urql/next (and replaces next-urql), the goal is to achieve good Next 13 support.

In essence this creates two new entry points

• @urql/next the entry points for components rendered on the server and hydrated on the client, this uses a few next-internals to hydrate data as DOM streams to the client
• @urql/next/rsc this solely intends to create a client that can be used and shared across
  server components. The sharing method is react.cache

You can play with an example here the main idea is that in Next we need a way to retrieve context values on the client so they can be shared. During the stream the values will be flushed, we use this to ensure we have all the data we need. In the example you can see that we have two suspense boundaries, neither will initiate a fetch on the client but instead you'll see a script tag get populated twice, one for each boundary. We read these <script tags and add them to the ssr-exchange.

TODO:

• resolve the build warning
• add an example
• check if we can find a good way of testing this (spoiler: nope)
• update documentation
• find a way around the key warning for <script />
• find a way to add "use client" to the @urql/next entry-point
• think about handling text/event-stream and multipart/mixed, do we just remove @defer and @stream during ssr? Or can we add a mechanism that ensures these are handled correctly i.e. by means of a useFragment-like mechanism throwing promises as well

Having an awkward problem where it's not letting me create a changeset on my fork 😅

People can still use next-urql for the old next supported ways

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
urql-docs	⬜️ Ignored (Inspect)	Visit Preview		May 29, 2023 6:09pm

[kitten]

Just some minor questions. Sourcemaps question is the only relevant for publishing and correctness.

We're missing TSDocs for the public APIs, but I think I can add those later on before publishing as well

[JoviDeCroock]

Should I copy the useQuery TSDocs from the react implementation or is there a way to inherit?

EDIT: @inheritDoc doesn't do much in VSCode atleast

[kitten]

LGTM 👍 I haven't tested this in code, but I think we can release this as a prerelease and see what happens 😄 Wdyt?