-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prisma2 init
does not find ts-node
when using starter kit "GraphQL API (+ Auth)"
#482
Comments
I can confirm this. It is an easy workaround for now as you just need to run |
FYI: Still occurs in version |
|
@ttsirkia Yes, the issue however is that these dev deps exist and are installed but for some reason |
On further digging, I can confirm that using the That is used here and it breaks the Tim informed me that a proper fix for this is to refactor the Handing this one over to @timsuchanek |
Fixed in the latest alpha. |
I can still reproduce this with
Note that the workaround of manually running |
Can confirm that the same procedure still fails when using version |
Apologies for the problems! We released a patch to fix this! |
Using Prisma 2 version:
prisma2@2.0.0-preview-9.1, binary version: bbbeff6f84b408e534ebd866bfd378748e6d6611
When running
prisma2 init
with the GraphQL API (+ Auth)starter kit I came across the following error. I assume that thenpm install
did not install everything:After running a
npm i
I could runnpm run seed
successfully.The text was updated successfully, but these errors were encountered: