// the take
The official GraphQL module for NestJS, wrapping Apollo Server (or Mercurius) behind Nest's decorator-based module system. It's for teams already on Nest who want GraphQL instead of REST and don't want to wire up schema generation, resolvers, and federation by hand.
Supports both code-first (decorators generate the SDL) and schema-first (you write .graphql files, it generates TypeScript types) without forcing one approach on the whole app. Apollo Federation and gateway support is first-class, with its own driver and a real e2e test suite covering gateway composition, async module config, and subscription edge cases. Maintained in lockstep with the rest of the Nest monorepo via lerna, with CI, commit linting, and a recent push history that shows this isn't an abandoned side package.
You're locked into reflect-metadata and TypeScript's experimental decorators for the code-first path, which is awkward if your tsconfig is moving toward the stage-3 decorator standard. It doesn't solve N+1 queries for you — DataLoader batching is still on you to wire into resolvers. Federation gateway support is tied tightly to @apollo/gateway's version, and that package has broken compatibility across majors before, so upgrades aren't always drop-in. Error formatting defaults to Apollo's shape, which can leak stack traces or internal error codes to clients unless you explicitly configure a formatError hook.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →