then, my package is added in

/node_modules

but, I should compile it for can to work, but is not

anyone?

here is my steps: 1. Install package from fork 2.

cd node_modules/graphql-tools && npm i && npm run compile

3. Try use my fork, and so crashes.

Is there any way to hook Prisma into an existing (running)

nodemon

?

Hi, how does Prisma handle 1-1 relationships on the User node? When I change the User Model from the authentication sample (https://github.com/graphcool/prisma/tree/master/examples/auth) to take only one post (change posts: [Post!]! to posts: Post!) I get an error when i create a new user saying i need to supply the post. What would be my strategy for a 1-1 relation like that? I cant create the post first, because it requires the user id, but i cant create the user because it needs the post. any ideas here? Or am I misunderstanding something?

do people have any thoughts on running your own graphql-yoga server with prisma backend vs. graphcool-framework?

anyone with experience deploying graphql-yoga to AWS Lamdba?

@eele commented on @vistriter’s file : Shouldn't you use the subscription api endpoint instead of the simple endpoint?

Really nice job on Chromeless. I am an SEO and was thinking of compiling what Google uses to crawl (Chrome 41) and implementing via serverless chrome as Google's tools for testing what they "see" are quite limited for debugging. Wanted to see if that was a waste of time before I got started.

I’m working on the Hackernews clone tutorial. I’m getting this error: `Server is running on http://localhost:4000 Error: Invalid Prisma endpoint provided: __PRISMA_ENDPOINT__ at new Prisma (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/prisma-binding/dist/Prisma.js7519) at GraphQLServer.context (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/src/index.js209) at GraphQLServer.<anonymous> (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js19151) at step (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js4023) at Object.next (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js2153) at /Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js1571 at new Promise (<anonymous>) at __awaiter (/Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js1112) at /Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/graphql-yoga/dist/src/index.js184108 at /Users/erichodges/Documents/Coding/graphcool/hackernews-react-apollo/server/node_modules/apollo-server-core/dist/graphqlOptions.js5240 ^C ➜ server prisma info Service Name: hackernews-graphql-js dev (cluster:

prisma-us1

) HTTP: https://us1.prisma.sh/public-rosehead-346/hackernews-graphql-js/dev Websocket: wss://us1.prisma.sh/public-rosehead-346/hackernews-graphql-js/dev` I checked the endpoint, and it’s correct in the index.js

what’s the best way to reset data with Prisma? I’m trying to get rid of all the

Posts

I’ve created but when I run

prisma reset

I can still see the data when I query

{
  posts {
    id
  }
}

Still a work in progress, but building a client based on the prisma airbnb clone example: https://entr-www.netlify.com/?AND%5B0%5D%5Bpricing%5D%5BperHour_gte%5D=435&amp;AND%5B1%5D%5Bpricing%5D%5BperHour_lte%5D=1287 Edit: you will notice that the URL is basically the arguments for the prisma query lol

I did notice that any custom resolver i implement slows down my queries tremendously, and i am assuming this is because of the shared clusters. I guess the best option would be to host on DO until Prisma Cloud is released i believe

Is it possible to see logs for all queries/etc against my graph.cool endpoint(s)? Including IP addresses or something similar?

hey all! just wanted to come in and throw my support behind Prisma. It's too early for us to use at work, but I'm going to be hacking on it nights and looking forward to seeing it develop 👍

Hey 👋 Does anyone know how I can add

.env

to

graphcool-framework

deployment?

Now I’m working on the Prisma Auth example. I’m getting this error:

Server is running on <http://localhost:4000>
[Network error]: FetchError: request to <http://localhost:60000/myapp/dev> failed, reason: connect ECONNREFUSED 127.0.0.1:60000
Error: request to <http://localhost:60000/myapp/dev> failed, reason: connect ECONNREFUSED 127.0.0.1:60000
    at Object.checkResultAndHandleErrors (/Users/erichodges/Documents/Coding/graphcool/auth/node_modules/graphql-tools/dist/stitching/errors.js:69:36)
    at Object.<anonymous> (/Users/erichodges/Documents/Coding/graphcool/auth/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:92:52)
    at step (/Users/erichodges/Documents/Coding/graphcool/auth/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:40:23)
    at Object.next (/Users/erichodges/Documents/Coding/graphcool/auth/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:21:53)
    at fulfilled (/Users/erichodges/Documents/Coding/graphcool/auth/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:12:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

@ehodges that just means there is something else using your 6000 port

run

killall node

and start the server again

try that

it means nothing is running on 60000

yes

ah

sorry lol, the opposite. @harmony is right

ok, so what do I do?

is this a docker issue?

we don't have enough information to help you out with that

Prisma Auth example: I made additions to the datamodel on the user type. I ran prisma deploy and the console said the new fields were made. I reloaded the playground and the changes are not in the schema. What am I missing? More mystery: I get the new additions to the schema in the desktop playground, along with a bunch of other things that are not in the web based version...except the signup mutation. What's up with that?