get-graphql-schema VS graphql

The other case is useful when we want to work on the frontend without being affected by the internet connection. In this case, the schema has to be the same as the live one. We can easily get the same schema from the backend by downloading it with the help of some tools, like graphql-cli{target=_blank} or get-graphql-schema{target=_blank}.

Let’s use the official documentation to follow the correct setup Documentation | NestJS - A progressive Node.js framework

Also use Express and Apollo, following Quick start.

This code demonstrates the centralized addition of a guard to a module, and by the way, NestJS v9 still doesn’t support this feature. In NestJS, adding a guard is supported only at the controller or method level, because the guard is not considered a provider.

To change your NestJS API into GraphQL, follow the GraphQL quickstart with NestJS and import the following code to your AppModule in src/app.module.ts.

Nest.js is an excellent alternative for GraphQL APIs building for Angular design and DDD lovers. Nest.js comes with:

[NestJS](https://docs.nestjs.com/graphql/quick-start)

I am interested in getting subscriptions working with federation. One solution I think is to run a separate non-federated end-point but I think NestJS has a bug where is merges the schemas. https://github.com/nestjs/graphql/issues/721 has been locked for over a year :(