Engine binary location configuration conflicts with mirror fallback

5/10 Medium

When custom engine locations are specified in .env, Prisma still attempts to fetch checksums from the mirror instead of respecting the custom configuration, causing unnecessary network calls.

Prisma
Category
config
Workaround
none
Stage
build
Freshness
persistent
Scope
single_lib
Upstream
open
Recurring
No
Buyer Type
team
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Prisma for developers in 2025?”4/4/2026

`prisma generate` tries to fetch engine checksum files from mirror even if custom engine locations are provided in an `.env` file

Created: 4/4/2026Updated: 4/4/2026