@thdxr, had an idea that I tried this morning: Not using any framework (besides graphql.js, “graphql” in npm) or running a server at all for a graphql lambda. Was surprisingly easy, and even Apollo specific things like

apollo-server-errors

work out of the box (because

apollo

uses graphql.js). ESM now works, and my package size dropped by ~1.8MB, which made cold starts about half as long. Happy to share more if it is interesting.

that's almost what we're doing in the new graphql stack

I am assuming express is involved (helix typically works this way), so the added bulk might actually be kinda significant. express v4.17.3 ❘ Bundlephobia

Express isn't involved! Helix isn't a GraphQL server itself it's just utility functions, we wrote the connect to AWS lambda events

alright, that sounds close enough, certainly. You can rest assured telling people it is a solid replacement, we have a fairly complicated use case and leaned heavily on Apollo, and it was still really, really easy. I think the only thing that would hang people is caching or middleware.

that's a good point we should keep that in mind

I am using

graphql-compose

for these types of purposes, but my experience has been mixed. It definitely works. I don’t have experience with Helix to compare.

yeah that'll be helpful, I'm happy with where the base is but I'm not sure what happens when you have a bunch of resolvers + real code in the mix

No issues at all, aside from one interface change from

graphql

15 to 16 (resolveType for unions)

do you have some sample code converting a lambda event into something that invokes a GraphQLSchema in graphqljs?

@thdxr

const handler: APIGatewayProxyHandlerV2WithJWTAuthorizer = async (
    event,
    context
) => {
    const graphqlContext: LambdaContextFunctionParams<
        DataLoaders,
        undefined
    > = {
        event,
        context,
        express: undefined,
        loaders: dataLoaders,
    };

    if (!event.body) {
        throw new Error("No body");
    }

    const parsedBody = JSON.parse(event.body);

    graphQlLogger.log("Request started! Query:\n" + parsedBody.query, {
        label: "handler",
    });

    const response = await graphql({
        schema,
        source: parsedBody.query,
        contextValue: graphqlContext,
        variableValues: parsedBody.variables,
    });

    return {
        statusCode: 200,
        body: JSON.stringify(response),
        headers: {
            "Content-Type": "application/json",
        },
    };
};

nice thanks will look at this soon

Realized that the dataLoaders should be INSIDE the handler, just an FYI.