In my project, I configured .graphqlconfig.yaml like this

projects:
  app:
    schemaPath: src/schema.graphql
    extensions:
      endpoints:
        default: '<http://localhost:4000>'
      prepare-bundle: src/generated/app.graphql
      codegen:
        - generator: prisma-binding
          language: typescript
          output:
            binding: src/generated/app.ts
  prisma:
    schemaPath: src/generated/prisma.graphql
    extensions:
      prisma: prisma/prisma.yml
      codegen:
        - generator: prisma-binding
          language: typescript
          output:
            binding: src/generated/prisma.ts

Apologies I missed your reply to this. I have a few questions: - What command do I need to run to generate TypeScript definitions using the above? When I run

graphql codegen

I get:

TypeError: Cannot read property 'type' of undefined

- Where does src/generated/app.graphql come from? Is that generated by running

graphql codegen

?

check this https://github.com/prismagraphql/prisma/tree/master/examples/hooks

This only seems to relate to prisma definitions. I’d like to get TypeScript definitions for my

graphql-yoga

server.

I see! you have to transfer this configuration to the server part: https://github.com/prismagraphql/prisma/blob/master/examples/hooks/.graphqlconfig.yml#L8-L12

What command do I need to run to generate TypeScript definitions using the above?

There are 3 steps. 1. Run

graphql get-schema --project prisma

to generate

src/generated/prisma.graphql

2. Run

graphql prepare

to generate

src/generated/app.graphql

from

src/schema.graphql

3. Run

graphql codegen

to generate

src/generated/app.ts

and

src/generated/prisma.ts

from

src/generated/*.graphql

files.

Sorry for missing this again - thanks so much for your reply. I’ve run the above commands, but

graphql prepare

doesn’t seem to output anything at all. The contents of my

.graphqlconfig.yml

is here: https://gist.github.com/jonlambert/e8db2819d30bacf65d4064d90ab50f6a

I found typo in your .graphqlconfig.yml. please try again!

Thanks dude. Good catch! I looked over that completely

it seems that your

schema.graphql

is not correct.