What is this request about?
Add or explicitly finish the Fastify gateway HTTP adapter path so @atls/nestjs-gateway is not permanently limited to Express after the Apollo Server migration.
Describe the implementation plan
Split the gateway HTTP transport integration by Nest adapter type. Keep shared GraphQL Mesh orchestration in the common handler path and isolate Express/Fastify-specific request wiring in adapter-owned modules. Use the maintained Fastify Apollo integration only after the Express migration has stabilized the shared Apollo Server setup.
Task definition of done
GraphQLMeshHandler no longer throws Only express engine available for a supported Fastify setup.- Express-specific and Fastify-specific request wiring are separated by clear adapter ownership.
- Public module options describe which transport options are shared and which are adapter-specific.
- Fastify coverage proves GraphQL HTTP requests work through the Nest Fastify adapter.
- Express coverage remains green after Fastify support is added.
What is this request about?
Add or explicitly finish the Fastify gateway HTTP adapter path so
@atls/nestjs-gatewayis not permanently limited to Express after the Apollo Server migration.Describe the implementation plan
Split the gateway HTTP transport integration by Nest adapter type. Keep shared GraphQL Mesh orchestration in the common handler path and isolate Express/Fastify-specific request wiring in adapter-owned modules. Use the maintained Fastify Apollo integration only after the Express migration has stabilized the shared Apollo Server setup.
Task definition of done
GraphQLMeshHandlerno longer throwsOnly express engine availablefor a supported Fastify setup.