Possibility to emit schema file in offline context

[JohannesKlauss]

Currently, the plugin only emits a schema file on runtime, but this is not ideal for designing a microservice architecture, when other services depend on that schema file for generating their own code.

Is there a possibility to emit the schema file without having to run the NestJS server?

[MichalLytek]

NestJS has some mechanism to do that:
https://docs.nestjs.com/graphql/generating-sdl

However, it doesn't use modules but explicit resolvers class array, which is an awful idea.

You can do the same thing just by using buildSchema imported from type-graphql.
You can put emitSchemaFile option or use emitSchemaDefinitionFile function explicitly.

I will leave that issue open to create TypeGraphQLSchemaBuilderModule which gonna accepts modules and which gonna have method for emitting SDL instead of importing printSchema requirement.

[Borales]

@MichalLytek hi, any update on this?

[Borales]

@MichalLytek It is kind of a blocker for me, as I have a nestjs-powered backend (and I'm using code-first approach) for my graphql schema. And my client app uses graphql-codegen to generate graphql queries - but it needs a schema file to do that. On CI/CD - I want to be able to generate my schema file so that codegen would be able to generate the queries (as I can't start the app on a CI service).

The suggested solution with buildSchema - doesn't work properly, as it's missing the whole NestJS infra. I specified the resolvers glob pattern - it then started complaining it wasn't able to import other classes.

Or the emitted schema file is supposed to be git-tracked?

[Borales]

@MichalLytek I'm using typegraphql-prisma and typegraphql-nestjs. So all my types are generated from Prisma schema. And I tried following buildSchema suggestion (to compile the schema via resolvers):

import 'reflect-metadata';
import { buildSchemaSync } from 'type-graphql';

const schema = buildSchemaSync({
  resolvers: [__dirname + '/../src/graphql/**/*.resolvers.ts'],
  authChecker: () => true
});

It kinda works, but it exports all Prisma definitions (which I don't need). Emitting the file during runtime (with TypeGraphQLModule) - creates a proper schema file for the types with the declared resolvers (intended behavior).

Any other suggestions?

[MichalLytek]

@Borales you need to provide the imported resolvers explicitly in order to not emit all prisma definitions.