Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ENOENT running prisma2 init
See original GitHub issueHello I’m getting this error running the cli on:
- macOS Mojave
- prisma2@2.0.0-preview-6
- node v12.5.0 (npm v6.9.0)
prisma2 init hello-prisma2
Error: ENOENT: no such file or directory, scandir '/Users/juan/repos/hello-prisma2'
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:6 (2 by maintainers)
Top Results From Across the Web
ENOENT error on post deployment hook - Questions - Prisma 1
Fully working cluster, I'm trying to get db schema on 1.7 by post deployment hook No errors from deployment part but this in...
Read more >Best practice for instantiating PrismaClient with Next.js
The solution in this case is to instantiate a single instance PrismaClient and save it on the global object. Then we keep a...
Read more >Seeding your database - Prisma
This can be any command, prisma db seed will just execute it. ... In the seed.ts file, import Prisma Client, initialize it and...
Read more >Graphcool ENOENT error - Questions - Prisma 1 Forum
graphcool-framework init leads ... Error: ENOENT: no such file or directory, lstat '/Users/edankrolewicz/.graphcool' ... Command.run ...
Read more >How to seed a database with Prisma and Next.js - PlanetScale
Before you can run a seed script, you'll need to push this schema to your database. Terminal. npx prisma db push ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Running into the same issues since updating to
prisma2@2.0.0-preview-7, binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054In the meantime, after a simple
mkdirwith the full path outputted in the error message (e.g.mkdir /Users/juan/repos/hello-prisma2) I was able to rerunprisma2 initwithout error.Just created a PR for this one: https://github.com/prisma/prisma2/pull/376