inconsistency between `PRISMA_CLI_BINARY_TARGETS` and `binaryTargets`
See original GitHub issueBug description
native
is not allowed in PRISMA_CLI_BINARY_TARGETS env (it’s a valid value in binaryTargets
)
How to reproduce
PRISMA_CLI_BINARY_TARGETS=native,linux-musl yarn prisma generate
it will shows:
Error: Unknown binaryTarget native and no custom binaries were provided
Expected behavior
should works like binaryTargets
?
Environment & setup
- OS: Mac OS
- Database: MySQL
- Node.js version: 14.16.0
- Prisma version: 2.21.2 (e421996c87d5f3c8f7eeadd502d4ad402c89464d)
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the quick response.
tried the
BINARY_TARGETS
approach and it works like a charm. I ever thought thePRISMA_CLI_BINARY_TARGETS
was the implicit way to do the same here.And i just noticed that a single
linux-musl
inbinaryTargets
is enough to runprisma generate
on ubuntu (just a Warning), becauseprisma
will always downloading the native query engine ? Do I understand correctly?Thanks again.
sure 👉 #7295