Hello after I ran `prisma deploy` on one of my projects it w Prisma #orm-help

Hello! after I ran `prisma deploy` on one of my pr...

aroman

07/27/2018, 1:49 PM

Hello! after I ran

prisma deploy

on one of my projects it wont start up after

yarn start

. I keep getting this error:

Copy code

yarn run v1.7.0
warning ../package.json: No license field
$ yarn env-build && ./node_modules/.bin/ts-node src/index.ts
warning ../package.json: No license field

package json license:

"license": "ISC",

Can anyone point me in the right direction?

Jenkins

07/27/2018, 2:12 PM

Any other errors? Does it print anything? Are you running

yarn start

from the directory where

package.json

is located?

aroman

07/27/2018, 2:14 PM

No other errors. It is not printing anything. I am running

yarn start

from my root directory.

aroman

07/27/2018, 2:14 PM

Copy code

cc-aroman-mbp:repo_name aroman$ yarn start
yarn run v1.7.0
warning ../package.json: No license field
$ yarn env-build && ./node_modules/.bin/ts-node src/index.ts
warning ../package.json: No license field
$ ./node_modules/.bin/ts-node ./config/env.ts
✨  Done in 1.83s.

Jenkins

07/27/2018, 2:17 PM

That's odd. Have you tried changing something in the schema and trigger another deploy? Also, since you're using TS, have you regenerated your binding?

aroman

07/27/2018, 2:25 PM

So it was working before. I added a query to my app

schema

, did prisma deploy and tried to bounce the server, thats when I started getting this error. I did regenerate my bindings. Hmmm I just removed the query from my app

schema

and it worked. Must be due to not having added it’s counterpart on the database

schema

? The reason why I didn’t add on the db

schema

it’s hitting an external service

aroman

07/27/2018, 2:27 PM

NVM I figured it out. I was missing

scalar JSON

on my schema types. Thanks for your input!!

Jenkins

07/27/2018, 2:32 PM

Woopwoop! Gz! 🙂 And no worries! Always happy to help! 🙂

2 Views

Open in Slack

Previous Next