Replies: 8 comments 11 replies
-
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? |
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work? Our error message suggested you to copy the engine somewhere. How did that go? Which package manager are you using? Is your workspace a monorepo setup? Is your setup hosting multiple packages in a single workspace? Is a bundler in use? If yes, which one? Are you using webpack, swc, esbuild, rollup, or any other bundler? Is a framework in use? If yes, which one? Are you using Next.js, Next, or any other framework? Your project uses TypeScript or just JavaScript? Do you prefer using TypeScript or JavaScript within your project, or both? When you saw our message, did it happen locally or in deployment? The message was "Please help us by answering a few questions". Where is your project deployed? Are you deploying to Vercel, Netlify, Lambda, or something else? |
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work?The engine already exists. It looks like Prisma is trying to delete it. Which package manager are you using?NPM v10.2.3 Is your workspace a monorepo setup?No Is a bundler in use? If yes, which one?No Is a framework in use? If yes, which one?No Your project uses TypeScript or just JavaScript?Only JavaScript When you saw our message, did it happen locally or in deployment?Locally Where is your project deployed?^^ Currently running locally |
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work? Prisma version: 5.1.1
|
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work? Which package manager are you using? Is your workspace a monorepo setup? Is a bundler in use? If yes, which one? Is a framework in use? If yes, which one? Your project uses TypeScript or just JavaScript? When you saw our message, did it happen locally or in deployment? Where is your project deployed? [EDIT] The suggested workaround with the webpack plugin worked for me. ✅ |
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work? I ran Which package manager are you using? NPM 10.2.4 Is your workspace a monorepo setup? Yes. Is a bundler in use? If yes, which one? Yes, Vite on the frontend and tsup for data-access layer code that does prisma stuff. Is a framework in use? If yes, which one? Yes, Astro. Your project uses TypeScript or just JavaScript? All TypeScript. When you saw our message, did it happen locally or in deployment? Locally. Where is your project deployed? Docker on-prem. |
Beta Was this translation helpful? Give feedback.
-
Have you tried to copy the engine in the suggested location? Did that work? Yes. Because I'm using Which package manager are you using? pnnpm Is your workspace a monorepo setup? Yes Is a bundler in use? If yes, which one?
Is a framework in use? If yes, which one? Elysia Your project uses TypeScript or just JavaScript? TypeScript When you saw our message, did it happen locally or in deployment? Locally, inside a Dockerfile build Where is your project deployed? Docker. Railway Other Info I'm trying to build my app via Docker, and was able to work around this by adding these lines to my Dockerfile:
Unfortunately this isn't ideal though as it means anytime I upgrade Prisma I'm going to have to update these paths in my Dockerfile |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hi, you have been directed to this issue because we want to learn more about your project setup. Thanks to your answers, we will be able to make better design decisions in the future.
We'd appreciate it if you could take 5 minutes to answer a few questions for us. You can write your reply directly in this issue as a comment. Copy and paste these questions in your answer, and leave the answer blank if you don't know.
Have you tried to copy the engine in the suggested location? Did that work?
Our error message suggested you to copy the engine somewhere. How did that go?
Which package manager are you using?
For instance
npm
,pnpm
, oryarn
. Please attach the version if you know it.Is your workspace a monorepo setup?
Is your setup hosting multiple packages in a single workspace?
Is a bundler in use? If yes, which one?
Are you using
webpack
,swc
,esbuild
,rollup
, or any other bundler?Is a framework in use? If yes, which one?
Are you using
Next.js
,Next
, or any other framework?Your project uses TypeScript or just JavaScript?
Do you prefer using TypeScript or JavaScript within your project, or both?
When you saw our message, did it happen locally or in deployment?
The message was "Please help us by answering a few questions".
Where is your project deployed?
Are you deploying to Vercel, Netlify, Lambda, or something else?
Beta Was this translation helpful? Give feedback.
All reactions