Prisma

I now realize that what failed is the query engine download, I could cache it locally or simply run `npx prisma generate` as part of the Docker build step and have it cached as a side effect.

Hi <@U042HRM56AU> :wave:

We must have missed this in the sea of messages. We're glad you could figure out what the issue was. If you have any other queries, don't hesitate to ask in this channel.

The context was deploying to an on-prem air-gapped systems with no access to lazily fetch the query engine on demand

What I did is simply trigger the `npx prisma generate`, docker commit and then gave my customer this Docker.
IMHO this is a stopgap solution / workaround and it’s a bit odd that packages are not self contained as it happens to me only with Prisma, the rest of my npm packages are self contained.

In general when you rely on 3rd parties, e.g. plugins / extra drivers, then things can get messy, just like in the Prisma case

An “offline installation” of Prisma would probably be great, but again it’s not critical since I have a work-around