Any working examples with postgres, running into some problems getting everything started

What is the better way to authentication in prisma graphcool?

give me a reference

to how to do the authentication with prisma graphcool

I'm using prisma-eu1 and i get the error

Whoops. Looks like an internal server error. Search your cluster logs for request ID:

I can't find any documentation on how to search the logs, anyone know?

I am experiencing the same but on us-west-2

after upgrading to Prisma 1.7 , when you do graphql create testapp --boilerplate and hit enter and choose node-advanced, you will get no folders.

A file was commented on

yes i opened an issue there too , and yes i am using windows

Why prisma init local become so brainf**k?(((

Working projects broken after upgrade

Hello, anyone getting the following after upgrading to the latest graphql-yoga:

Error: Cannot find module 'graphql-yoga'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
    at Function.Module._load (internal/modules/cjs/loader.js:497:25)
    at Module.require (internal/modules/cjs/loader.js:626:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/Users/Sammy/Projects/ivnt-gql/src/index.ts:1:1)
    at Module._compile (internal/modules/cjs/loader.js:678:30)
    at Module.m._compile (/Users/Sammy/Projects/ivnt-gql/node_modules/ts-node/src/index.ts:402:23)
    at Module._extensions..js (internal/modules/cjs/loader.js:689:10)
    at Object.require.extensions.(anonymous function) [as .ts] (/Users/Sammy/Projects/ivnt-gql/node_modules/ts-node/src/index.ts:405:12)
    at Module.load (internal/modules/cjs/loader.js:589:32)
[nodemon] app crashed - waiting for file changes before starting...

P.S. Actually even after downgrading I’m now constantly getting this message 😞 This resolved it for now:

import { GraphQLServer } from 'graphql-yoga/dist';

@picosam this one reason of many, why my projects are broken after upgrade

run in server/ , but cjs in root of project, /node_modules/

Yep known issue on GitHub

I've pinged @schickling and I'm sure others have.

You can get it working locally if you clone the package and update

tsconfig.json

rootDir

to be

.

instead of

src

. Out right now so I can't submit PR and check this doesn't break anything else that came with

ava

.

@notrab Can you say how init prisma@1.7.3 local fullstack react project? With editable files and etc.

All examples are not actual now

Last working

graphql-yoga

was

1.9.0

afaik.

@notrab thanks! Will try now

(node:26108) UnhandledPromiseRejectionWarning: GraphQLError: Syntax Error GraphQL request (82:1) Unexpected String

81: 
82: """
    ^
83: An object with an ID

🙂

So I have made fresh install of latest Prisma in docker and when I try to deploy in there, I am getting ...

Authentication token is invalid: Token can't be decoded: Expected token [null] to be composed of 2 or 3 parts separated by dots.

I am unsure where would I put that token, there is no mention of that anywhere 😞

Hello everybody! Has anyone else experienced any issues, with using prisma init on version 1.7.3? When I select "Use existing db", I'm asked for the credentials but after the line "Connecting to database..." nothing happens at all. In fact the whole terminal freezes. BTW I'm on Windows 10. Thanks in advance! 🙂

@pasa i tryed all (on ubuntu 17). With mysql work after config twig tuning, but i have not own schema and server js files. It`s too hard to use

Gods! I can restore project from yarn.lock! :fast_parrot:

1.7 is hell of the update ... I can understand they are trying to give us more control, but things are suddenly so complicated and even broken in some cases ... I do love Prisma, but I think there should be a slower pace for changing stuff so drastically 😕

the problem is , things get behind here and there like , when you do prisma init my-app it will only ask for the location and not the boiler plate options like before and if you run the boiler plate cl it won't make any folders

restored 1.6.3 broken to...

const user = await ctx.db.query.user({ where: { 
    username,
  } })

Error: Field "user" of type "User" must have a selection of subfields. Did you mean "user { ... }"?

Very very bad upgrade (((((