You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some cases when Prisma ignores the configs, provided by the user, but the user has no idea about that. For example, when Prisma runs on Netlify, it throws away anything the user specified in binaryTargets and downloads the query engine specified in the Prisma code.
Suggested solution
Print a warning in the terminal, notifying the user about that:
You are running Prisma in the Netlify. Your binaryTargets configs will be ignored. Please unset the NETLIFY variable if you need to install another engine for some reason: NETLIFY= yarn prisma generate
Alternatives
Get rid of such magic stuff altogether and just tell the users what kind of binaryTargets they should use for every platform, instead of doing it implicitly
The text was updated successfully, but these errors were encountered:
Deploying to other targets from Netlify's CI, like Cloudflare's edge functions, AWS lambdas and so on. Took me a lot of time to understand why Prisma silently ignores the binaryTargets.
Interesting. Can you open a new issue where you formulate that as a bug?
I think we were not aware of this use case, so never considered this to be a problem.
Problem
There are some cases when Prisma ignores the configs, provided by the user, but the user has no idea about that. For example, when Prisma runs on Netlify, it throws away anything the user specified in
binaryTargets
and downloads the query engine specified in the Prisma code.Suggested solution
Print a warning in the terminal, notifying the user about that:
Alternatives
Get rid of such magic stuff altogether and just tell the users what kind of
binaryTargets
they should use for every platform, instead of doing it implicitlyThe text was updated successfully, but these errors were encountered: