https://www.prisma.io/ logo
Join Slack
Powered by
On updating from 2.23 to 2.26, I’m getting ```#11 ...
# prisma-client
j
On updating from 2.23 to 2.26, I’m getting
Copy code
#11 51.92 ✔ Installed the @prisma/client and prisma packages in your project
#11 51.92 Error: Could not resolve @prisma/client.
#11 51.92 Please try to install it with npm install @prisma/client and rerun prisma generate 🙏.
That might not be enough to know what’s going on, due to our own setup, but changing nothing but the version makes our builds fail. Does anything stand out to anyone based on the versions?
j
Ugh.
Can you set 
DEBUG=*
or 
DEBUG=prisma*
and run the process again?
To debug this, obviously we would ultimately need a way to reproduce and understand this - so a reproduction project that shows the same behavior (without the complexity of a real projects) would be 💯 - but let's see if we can debug this first.
(We did change something about that logic, but were pretty confident about the changes we made so 🤔 )
j
I think I figured it out. I had 
prisma
in dev dependencies, which had been working for all versions till now. I moved that alongside the client, and our builds are green again.
j
That is actually how it should be.
So I am still concerned.
Can you tell me a bit more about your project setup? Mostly interesting where the 
package.json
lives, if some monorepo or pnpm stuff is in the game, or if there is anything else weird or special.
j
No monorepo, just in the base dir
Built in a docker container based on node
Copy code
COPY package*.json /
RUN npm ci
COPY . /service/
WORKDIR /service/
RUN npx prisma generate
RUN npm run build
j
That looks simple enough.
Can you quickly create that repo project and see if it also fails there?
Would be very thankful for that.
j
I can try in a bit. We use a custom base image which I can’t share, but I’ll try something on an official node image or something similar.
👍 1
r
Are you setting 
NODE_ENV
to production anywhere?
j
Just saw this. Yeah we are
Open in Slack
PreviousNext
Powered by