hi - is there any github example of React app + Prisma w/ custom resolvers? (Google didn't get me anywhere)

This is our open source app, maybe it's useful for you: https://github.com/Volst/new-food-order/blob/master/backend/src/resolvers/Query.ts

There is also this boilerplate – https://github.com/graphql-boilerplates/react-fullstack-graphql

thank you!! just to be sure, I'm running React app as frontent only (no nodejs server) - does that setup exclude custom resolvers?

If you're using Prisma, you should have a separate "GraphQL server" running as well, which your React app connects to. It's theoretically possible to connect React app straight to Prisma, but afaik, it's not suggested/best practice.

so it could run without nodejs on backend - eg. standalone on github pages ?

There's few parts to using Prisma in production – you have your React app which is hosted anywhere. The React app connects to a (Node) GraphQL server which you can host on Now for example. Then you have Prisma, which needs to be running on it's own server and that is what the GraphQL server talks to.

roger that, thank you again

You do not need to use React or Node or anything else specifically with Prisma (which is written in Java, I think). Because you get so much out of the box with GraphQL, and then Prisma takes that to a whole new level, it’s easy to see any graphql endpoint like Prisma as a ‘server’ substitute. But it’s best to think about Prisma as a ‘thin wrapper’ for your data service. For simple, non production cases, you could definitely get away with connecting right to the endpoint from your client—it will work. But, apart from the potential security issues, if you were to go this route, you’d be missing sooooo much of the GraphQL goodness that running an actual server in front of Prisma would allow you to do. For instance, are you familiar with schema stitching? It’s where you use one GraphQL server/schema to tie together disparate sources of data for a seamless client experience. It’s life altering. And, btw, if you set up GraphQL-yoga or Apollo Server in front Prisma you are already doing schema stitching. There is absolutely no reason why you couldn’t have 10 Prismas behind your server. Or maybe you want to return some relevant other data (like, weather, github information, reverse geocodjng, etc), you could do all of that right along side your calls to Prisma. Your client would never know. It’s beautiful. But It needn’t be that complex. I run my GraphQL ‘server’ on AWS Lambda. Apart from not supporting subscriptions, it’s nearly the same experience with no cost for idle time. Happy to talk further to help talk through getting you set up if you’d like.