3-Month Roadmap: June, July, August 2025

This quarter, we're focused on stabilizing and delivering the architectural investments we’ve made over the past six months — especially the new Query Compiler and Generator. We’re also taking the opportunity to ship long-awaited polish by graduating two popular preview features to General Availability.

Our top three goals:

1. Ship the Query Compiler to GA for all SQL-style First-Class Databases (FCDBs)
2. Promote the new prisma-client generator from EA to Preview and then GA
3. Graduate multiSchema and views preview features to GA

We also remain committed to resolving long-standing community issues. While we didn’t close as many as planned last quarter due to the complexity of the Query Compiler work, they remain high on our list.

1. Query Compiler → General Availability

The new Query Compiler replaces Prisma Client’s legacy query engine with a faster, more flexible TypeScript implementation. It’s a foundational shift that improves performance, simplifies deployment (no more native binaries), and unlocks long-term platform flexibility.

After releasing in Preview last quarter for several FCDBs, we now aim to promote the Query Compiler to GA for all SQL-style FCDBs.

Planned GA support:

MongoDB support is actively in development, but its non-SQL nature has required a different approach. We expect it to GA shortly after the rest.

2. New prisma-client Generator: EA → Preview → GA

The new prisma-client generator is a modern, ESM-compatible alternative to prisma-client-js. It’s currently available in Early Access, and this quarter we plan to promote it to Preview and then General Availability.

This generator provides a cleaner and more predictable codebase for modern environments — especially those that rely on bundlers or ESM-only runtimes.

What’s changing:

• Output is ESM-compatible
• Generated code is split into multiple files
• package.json and other node_modules conventions are no longer generated
• EA → Preview → GA (this quarter)

When GA is reached, we plan to deprecate the older prisma-client-js generator.

3. Long-Standing Preview Features to GA

The multiSchema and views features have been in Preview for some time, and are widely used in production. This quarter, we’re committing to promoting them to General Availability.

We’ll use this time to finalize any API decisions and ensure documentation is complete and accurate.

• multiSchema → GA
• views → GA

4. Community Issues: Still Top of Mind

Last quarter, we outlined a long list of community issues we hoped to close as part of these architectural changes. Unfortunately, we weren’t able to make as much headway as planned, given the unexpected complexity of the Query Compiler work.

We still intend to address these — and many are now unblocked or significantly easier to resolve. We’ll continue prioritizing them throughout the quarter and include updates in our release notes and issue tracker.

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

• @prisma/nextjs-monorepo-workaround-plugin is not able to handle multiple clients #18069
• Importing enum in browsers results in `Error resolving module specifier “.prisma/client/index-browser”.  #12504
• Add support for Deno #2452
• Support ES6 modules export / ESM #5030
• Unable to interop export * from "@prisma/client" in /home/[user]/Documents/[project]/packages/db/index.ts, this may lose module exports. Please export "@prisma/client" as ESM or use named exports instead, e.g. export { A, B } from "@prisma/client" #21474
• Using Prisma NextJS edge runtime leads to error #18763
• Set default values for schema url fields #222
• Module '"@prisma/client"' has no exported member 'PrismaClient'.ts(2305) #13672
• prisma generate, typings not updating in VSCode unless IDE is restarted. #14722
• prisma generate fails in yarn2 / yarn3 workspaces #8765
• ESM (.mjs) modules of TypedSQL client use CommonJS imports when generating to a non-default location #25259
• Prisma 6.12.0 - Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' #27754
• 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
• e.map is not a function error with prisma-client generator + queryCompiler #27511
• Nuxt 3, nitro, prisma-client: Identifier 'process' has already been declared in production server logs #26908
• [6.x] WebAssembly.instantiate(): Import #0 "./query_compiler_bg.js": module is not an object or function] #26880

Issues addressed by no more .env loading

• 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
• Add Support for More .env Files #3226
• Support multiple .env files natively #11050
• @prisma/client magically loading .env file (and mutating process.env in the process) #15620
• Change the default filename for loading environment variables to .env.local #15681

Other long-standing issues we really want to address

• 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
• Add option to skip unnecessary SELECT after create() #4246
• Client extensions that require use of a client-level method silently ignore transactions #20678
• Introspecting a part of existing database #807

More recent bugs we want to address

• Error: Invalid Prisma Dev state for "default". #27771
• [6.10.2] init script: using a script init with existing .env file causes an error #27488
• Foreign Key constraint P2003 on creating a relationship entry while updating #27288
• Using "queryCompiler" with Postgresql Adapter $queryRaw fails with 'cannot read properties of undefined (reading 'length')' #27263
• "Contact Us" page on website, doesn't work #27259
• $queryRawUnsafe('SELECT NOW();'); => Cannot read properties of undefined (reading 'length') #27257
• Creating a row with pg timestamptz array with Prisma throws error #27248
• [queryCompiler] ~ include: true, sometimes doesn't include #27240
• npx prisma init command is not working #27234
• SQLite fails with relative path when using custom output path in NestJS example #27212
• npx prisma init fails with ENOENT mkdir due to invalid path with embedded user directory #27206
• prisma init not working #27202
• 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
• prisma general omit for multi model fields does not work #27187
• Import errror from @prisma/client with client output defined #27169
• Prisma 6.7.0 Schema lookup change #27163
• PrismaPG: prismaClient unusable after calling $disconnect since 6.6.0 #27157
• 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
• ❗ Issue: Error P3006 when running npx prisma migrate dev --create-only after resolving migration from empty state #27108
• Prisma linting issues when deploye to Vercel #27087
• When the output path is inside the prisma directory, the database cannot be found #27085
• hi All, I am a newby and need some help with the schema setup for the following scenario: #27081
• [CLI] .gitignore file generated by prisma init should include output directory #27076
• security 6.7.0 prisma migrate update client files with db url value in clear #27074
• 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
• Type error in src/generated/prisma/internal/class.ts when upgrading to 6.7.0 with queryCompiler feature #27027
• thread '<unnamed>' panicked at query-engine #26963
• Error in Prisma Language Server after adding prisma.config.ts #26952
• Multischema support for tables with duplicate names not working (Sqlserver) #26899
• prisma-client: TypeError: __banner_node_url when using enums on the client-side #26897
• Nuxt, ESM, prisma-client: File URL path must be absolute error #26857
• Two tiny changes needed for Prisma 6.6.0 to work with Deno #26843
• [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
• Cannot migrate changes on Multi Schema setup for SQL Server #24068
• Sql Server migrations fail with multiSchema when schemas include "dbo" schema #23688
• [multiSchema previewFeature] The database schema is not empty error on prisma migrate deploy #23327