Prisma generate have different result in v5.13

I just upgrade prisma to 5.13 and it broke everything in my CI. It have different docker result between 5.12 and 5.13 When I downgrade it to 5.12, it runs without problem. my stack: bun + sveltekit automate using jenkins in v5.13, there is no log in the docker output:
#11 [ 7/10] RUN bunx prisma generate
#11 sha256:ae7c479d60dc00f8478c6a8ab33272dc2c7af766b0a5c541a1bb10b6d6e8f6b2
#11 DONE 1.9s
#11 [ 7/10] RUN bunx prisma generate
#11 sha256:ae7c479d60dc00f8478c6a8ab33272dc2c7af766b0a5c541a1bb10b6d6e8f6b2
#11 DONE 1.9s
while in v5.12, it have the usual prisma generate log:
#11 [ 7/10] RUN bunx prisma generate
#11 0.813 Prisma schema loaded from prisma/schema.prisma
#11 1.433
#11 1.433 ✔ Generated Prisma Client (v5.12.0) to ./node_modules/@prisma/client in 172ms
#11 1.433
#11 1.433 Start using Prisma Client in Node.js (See: https://pris.ly/d/client)#11 1.433
...... usual log
#11 DONE 1.7s
#11 [ 7/10] RUN bunx prisma generate
#11 0.813 Prisma schema loaded from prisma/schema.prisma
#11 1.433
#11 1.433 ✔ Generated Prisma Client (v5.12.0) to ./node_modules/@prisma/client in 172ms
#11 1.433
#11 1.433 Start using Prisma Client in Node.js (See: https://pris.ly/d/client)#11 1.433
...... usual log
#11 DONE 1.7s
I don't know if this have effect, but using 5.13 making my build inside docker failed. Maybe there is some broken change in prisma generate in 5.13 ?
2 Replies
Nurul
Nurul3mo ago
Hey 👋 If I understand correctly, you are not getting any output when you invoke npx prisma generate in version 5.13.0, right? But in 5.12.0 it works as expected.
PedasMampus
PedasMampus3mo ago
yes but when I tried it locally in my CLI it works