I've been banging my head against this for most of the day: I'm running my Next.js + Prisma app in Docker and have my Dockerfile set up similar to the https://github.com/vercel/next.js/tree/canary/examples/with-docker example. I've also added the prisma CLI to my dependencies, but Next.js will not include it in the final standalone build because it's not used directly in the code of my app. I need it to run migrations during server startup though (and would also like to occasionally run Prisma Studio from the same image by overriding the docker entrypoint). Is there a way to force Next.js to include the prisma dependency in a standalone build? I explicitly don't want to use npx here because that implies downloading the prisma dependency (and any necessary engine binaries) during runtime which is too fragile IMHO. I want to have everything baked into the final Docker image.