Next.js example

[matthewlilley]

Thanks for sharing these. I've tried using various of the examples provided in a Next.js application, I was hoping to use Apollo but failed to get it running smoothly. It would be useful to see some examples if you have the time to do that :)

[matthewlilley]

I think the issues I was seeing was when using Apollo, and more complex config with transforms. I tried again this morning and I was able to get data with the simple version, but lots of critical errors in console the moment I make it slightly more complex.

[ardatan]

@matthewlilley Could you share your example that has those errors?

[matthewlilley]

For context, we have around 15 identical subgraphs across different networks for our exchange. I'd like to query them all in one, with at least some simple transformations like prefixing ETHEREUM_, MATIC_, etc... and later would like to apply some schema stitching too. The basic example works great, but since they're the same I need transforms. I'd also like to use Apollo on the frontend so I can continue to get fresh data after the initial hydration from the server.

[matthewlilley]

@matthewlilley Could you share your example that has those errors?

Yeah, sure. Let me throw it up.

[matthewlilley]

You'll want to pull this branch

https://github.com/sushiswap/interface/tree/feature/analytics

• pnpm i
• pnpx turbo run dev
• pnpx turbo run dev --scope=analytics

This isn't using Apollo at the moment, and I get the data, but see a lot of these critical dependency warnings in terminal when visiting the page /analytics.

I'll try wiring up Apollo in the meantime, I never managed to get this working with any kind of transforms, I expect the simple version will work fine.

[matthewlilley]

#34

[matthewlilley]

It would be good to see a Next.js example with Apollo & urlq, right now both fail with the common errors you see with isomorphic web frameworks, e.g. "Module not found: Can't resolve 'fs'".

[matthewlilley]

Seems to always be issues like this when the generated library is imported on the client. I've only been able to make use on the server so far. I've never had a problem with Apollo in Next.js before so assume this is a graphprotocol/client or graphqlmesh issue.

[ardatan]

It is not this project specifically but GraphQL Mesh which Graph Client heavily uses under the hood. We deployed one of our example projects that use GraphQL Handler just like GraphQL Client to Vercel;

Logs; https://vercel.com/theguild/graphql-mesh/A3MASwMEGhpWbwj4scpPy6t1bhqj
Working endpoint; https://graphql-mesh.com/api/covid
Code; https://github.com/Urigo/graphql-mesh/tree/master/website/src/pages/api/covid

[dotansimha]

Hi there! With the recent upgrades in graph-client internals, we can see that running it in NextJS works fine :)
Please try @graphprotocol/client-cli@0.0.5

Seems like we might have a few more issues around this integration, @ardatan and @charlypoly are investigating.

UPDATE: Seem like #50 fixed it.