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.

Prisma 2.24.0 throws error `Query engine exited with code 101 - thread 'main' panicked at 'Could not open datamodel file "/schema.prisma"...'`

See original GitHub issue

Bug description

Everything works fine in 2.23.0

I am using nx with next and hosting on vercel

How to reproduce

Not sure I’ll be able to setup a minimal reproduction, but @janpio has access to our code to reproduce simply by upgrading to 2.24.0

Expected behavior

No response

Prisma information

Query runs during next build to do SSG. I don’t believe the actual schema is relevant

Environment & setup

OS: Debian (on vercel)
Database: PostgreSQL, MySQL, MariaDB or SQLite
Node.js version: 14.16.0

Prisma Version

2.24.0

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

wuichencommented, Jun 10, 2021

i think this happens specifically when you add output to prisma.schema’s generator client section. i am facing the same issue when pointing client generation at a different path. i think this is also the issue blocking other multi-data sources prisma access in monorepo.

1reaction

janpiocommented, Jun 14, 2021

Here are two issues about the _http_common thing: https://github.com/prisma/prisma/issues/6564 + https://github.com/prisma/prisma/issues/6925 (There are a bunch of workarounds in the comments like https://github.com/prisma/prisma/issues/6564#issuecomment-849685096)