How does `SchemaLink` fit in here?

Grabbing the example for Next.js [with-apollo-neo4j-graphql][1] before the `App` router became stable it used to check `isServer` (`typeof window === 'undefined'`) and based on that create a `SchemaLink`, which was supposed to use the same GraphQL query as a client instance, but be more efficient (I think it skips the HTTP request and queries the Schema directly, which in this example would be a Neo4jGraphQLSchema, not sure so don't quote me) but also limited to server-side components like SRC or SSR without the "use client" pragma (or whatever this metadata is called).

I'm wondering how this fits in the library since the README.md doesn't mention `SchemaLink`.

[1]: https://github.com/vercel/next.js/blob/deprecated-main/examples/with-apollo-neo4j-graphql/apollo/client.js#L8-L11

Start with README.md and the linked Next.js example at client.js lines 8-11, then review the existing integration documentation for SchemaLink coverage. Clarify whether SchemaLink is supported in this library and document its intended server-side use or limitations, with the README updated to match.

Written by the indexing model from the issue text.