Triggering resolvers when GraphQL Mesh v1 is used as a middleware

[KissG89]

Dear Members,

I’m currently upgrading from Mesh v0 to v1, and since v1 works quite differently, I’d like to ask for your support.

My application is an express app with several REST endpoints. For the /graphql endpoint, I’m using the Mesh middleware:

app.use("/graphql", createBuiltMeshHTTPHandler());

This setup works perfectly — queries appear in GraphiQL, and when I execute one, the corresponding resolver is triggered as expected.

The other REST endpoints use Mesh’s generated SDKs for queries. This allows me to reuse the same logic for both REST and GraphQL, keeping the implementation consistent.

Here’s my new setup for Mesh v1:

const serveRuntime = createGatewayRuntime({
  supergraph: "./supergraph.graphql",
});

Unfortunately, this approach doesn’t trigger my resolvers, meaning I can’t use my custom schemas.

I have two questions:

1. In the new Mesh version, how can I register my resolvers so that when a query is called in GraphiQL (or in any other ways), it correctly invokes the associated resolver function?

2. How can I generate SDKs for my queries?
   In the Codegen configuration, I know I need to add the documents property to generate the functions — but does that mean I now need to implement the queries in addition to the typedefs?

Thank you in advance!