I'm getting some weird issue that I haven't had before so I'm using the graphql boilerplate that and the genrated file prisma.graphql Does not update

You mean it doesn't update after you ran

prisma deploy

?

Yes

Can you see if the

post-deploy

hook that's configured in

prisma.yml

is being invoked when you run

prisma deploy

? It should print smth like this:

post-deploy:
Running graphql get-schema --project database ✔

Yes it's running

post-deploy:

Running graphql get-schema --project database...

However when I do changes to the data model what’s getting updated is the endpoint not the generated file.

Also, what happens when you're running the command directly in the terminal:

graphql get-schema --project database

Does it update then?

Not it's not getting updated, can confirm it now after three attempts however what is getting updated is the actual endpoint

Are there any errors?

When I run the npm run prisma deploy I'm getting this error

post-deploy:

spawnSync graphql ENOENT

Running graphql get-schema --project database ×

Other than that I'm not getting any real errors

Ah, seems like this a know issue already: https://github.com/graphql-cli/graphql-cli/issues/354

Any solution for this I really like the boilerplates

I've just posted a workaround in the issue: https://github.com/graphql-cli/graphql-cli/issues/354#issuecomment-438291628

thank you @nikolasburk ! I was getting close to insanity with this issue xD. But what's wrong with the post-deploy?