Dotan Simha

Hi there! With the recent upgrades in `graph-client` internals, we can see that running it on node14 works fine :) Please try `@graphprotocol/[email protected]` and let me know if we need...

> @dotansimha looks like this needs to be re-opened. This happens because Webpack tries to bundle all code, and not just the runtime code that's used (which makes sense...). The...

Perfect! I see @ardatan already released `cross-undici-fetch` (https://github.com/ardatan/whatwg-node/blob/master/packages/cross-undici-fetch/package.json#L25). So now the missing piece in that puzzle is: release GraphQL-Mesh -> then we can upgrade and release `graph-client`. In the meantime,...

@matthewlilley can you try `@graphprotocol/[email protected]`? :) It should use latest version of all packages, and should solve this issue.

Yeah, sometimes NPM needs a few minutes after publishing a new version :) https://www.npmjs.com/package/@graphprotocol/client-cli

> @dotansimha I think this is a reflection of the implementation in graph-node, I think you were looking into changing that? Yeah, we are still working on improving that in...

> @dotansimha @kamilkisiela Should we move this issue to graph-node? I'm working on a reproduction and then will open an issue with all the details. Thanks!

Hi @matthewlilley , I tested ~10 subgraphs with different setups ,but this does not reproduce at all. Can you please share a Subgraph + a query that produces invalid data...

> @dotansimha I've asked Lufy to make a repro. We can reproduce this quite easily in a lot of different cases. Will post shortly. Thanks! Please keep us updated :)...

@n1ru4l what do you think about this one? Basically, the tooling we are building in this repo will eventually have a remote executable schema (mesh/tools executor) that we can use...