github.com
Prisma ORM Roadmap: June - August 2025 · Issue #27503
Excerpt
**Issues addressed by Query Compiler** - Context propagation for query logging #7596 - `prisma generate` tries to fetch engine checksum files from mirror even if custom engine locations are provided in an `.env` file #12593 - Allow `binaryTargets` as a CLI option #15267 **Issues addressed by ESM Support + Driver Adapters** … - Error building locally a Remix v2 site in a sst v2 app #27719 - Types not exposed properly in monorepo with `prisma-client` provider #27600 - new prisma-client generator + queryCompiler: require() of ES Module #27572 - Prisma Postgres Adapter with Turborepo does not work #27083 … - Root `.env` variables aren't available to prisma in monorepo #12535 - Switch `.env` file based on `NODE_ENV` #3865 - importing prisma client pollutes `process.env` without using dotenv #19519 - Possibly reading `.env` file and schema twice #19117 … - Running `prisma migrate dev --create-only` actually applies previous (non-deployed) migrations #11184 - `migrate dev --create-only` with empty schema but existing database schema detects drift and warns about deleting all data #6579 - Allow calling `prisma migrate dev` programmatically by adding `--allow-non-interactive` flag #7113 - `prisma db reset` that resets the database, pushes the schema, and runs the seed function #11261 - `pnpm install` not running `prisma generate` #6603 - Large schemas generate huge `index.d.ts` causing slow autocomplete and type-checking in your editor #4807 … - 6.8.1 hotfix init error still exists #27195 - Prisma cannot find the prisma client module #27194 - Prisma 6.8.0 init error on Windows - Only URLs with a scheme in: file, data, and node are supported by the default ESM loader #27192 … - Generated client cannot be used on frontend #27156 - D1 adaptor throws "Conversion failed: expected a datetime string in column" when string column contains rfc3339 date #27143 - Fetching with `include` on one-to-one related field only gets first relation #27137 - bun run build error with prisma ^6.7.0 #27136 - `prisma generate --watch` always uses cached version of `schema.prisma` file #27128 - Query compiler cannot handle join on columns with @map defined #27111 - Sveltekit / Build step: "PrismaClient" is not exported by "../../packages/database/generated/prisma/index.js" #27109 … - can't import enums on browser from the new generated client (Vite) #27073 - [queryCompiler] undefined _count value when counting relations #27055 - How Prisma Client interacts with PgBouncer in session mode #27054 - [6.7.0] queryCompiler with pg has any retrieval of fields with dates be an empty object #27050 - queryCompiler: “TypeError: createRequire is not a function” #27049 - new prisma-client generator with next.js/webpack: can’t resolve `./client.js` #27048 - JSONB column not being parsed with queryCompiler #27039 - [Bug] [6.7.0] V6 unable to find existing migrations #27038 - [6.7.0] Schema ignored #27037 - [6.7.0] Client generated by prisma-client doesn't work with strictest tsconfig #27032 - [6.7.0] Apparent bug with `queryCompiler` feature (repro included) #27031 - [6.7.0] Bug: When using the queryCompiler feature, String[] fields are returned as comma-separated strings (e.g., "a,b,c") instead of proper arrays ([a, b, c]) #27029 … - [Postgresql] Dropping constraint will occur an unexpected error. #26622 - No relation tables generated when using views in many-to-many relations #26593 - Slow performance during create with CITEXT column #26400 - feat(@prisma/instrumentation): include additional query context (ideally db.query.summary) #26081 - Custom migrations path #26027 - `Option::unwrap()` on a `None` value for specific operations when enabling `relationJoins` feature #25802 - Possible memory leak using driver adapters with cloudflare D1 #25714 - createManyAndReturn fails with @ignore fields (field must be a known scalar or virtual) #25290
Related Pain Points
Prisma v6.7.0+ queryCompiler feature introduces widespread data corruption and parsing bugs
9The recently released queryCompiler feature in Prisma 6.7.0+ has introduced critical bugs affecting data integrity: JSONB columns return empty objects, String[] fields are returned as comma-separated strings instead of arrays, date fields become empty objects, and relations with @map fail to parse. Multiple users report broken functionality across PostgreSQL, D1 (SQLite), and other databases.
Prisma environment variable handling breaks in monorepos and ESM contexts
8Prisma struggles to correctly load `.env` files in monorepo setups, doesn't support NODE_ENV-based `.env` switching, and silently pollutes `process.env` without explicit dotenv usage. Recent versions (6.7.0+) have introduced critical ESM-related module resolution failures across Turborepo, Next.js, Remix, and other frameworks.
Prisma migration commands are unreliable and dangerous in non-interactive contexts
7Prisma's migration system has multiple critical bugs: `prisma migrate dev --create-only` applies previous pending migrations unexpectedly, `migrate dev` cannot be called programmatically, and `db reset` lacks the ability to reset and reseed atomically. These issues make CI/CD integration and automated workflows fragile.
Large Prisma schemas cause severe type-checking and autocomplete performance degradation
6When projects exceed 100+ database models, Prisma's type generation produces enormous `index.d.ts` files that slow down IDE autocomplete, type-checking, and overall editor responsiveness, creating a significant developer experience penalty for complex database structures.