Prisma ORM Roadmap: March – May 2025 · Issue #26592 - GitHub

This quarter, our two major objectives are to deliver the Query Compiler to *Preview* and to enable the Prisma CLI to work in web contexts, such as StackBlitz or other web-based editors. We’re also improving the developer experience by: - Making Prisma-generated code ESM-compatible - Splitting Prisma's generated output into multiple files instead of one large file - Refining some tricky CLI commands (looking at you, `migrate dev`) ... As always, we're addressing a curated list of high-priority community issues alongside these major projects — this time targeting around 30 issues. … ## 3. ... Going forward, we’re deprecating the following behavior: - A deprecation warning will appear unless you specify an output path for generated code - Starting with Prisma 7, specifying an output path will be required We're also improving code generation quality: ... - Code will be **ESM-compatible** - We will no longer generate a `package.json` — you can define it yourself if needed ... Finally, we’re removing Prisma’s automatic loading of .env files. The `prisma.config.ts` file allows you to manage environment configuration directly for CLI commands, and we believe your ORM shouldn’t handle this behavior for your production application. Currently, this behavior is already disabled if a config file is present but retained for backward compatibility. In Prisma 7, it will be removed completely. … **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 Web-Compatible CLI** - Support Migrations, Introspection, Studio for Driver Adapters only databases (e.g. Turso, Cloudflare D1) #22184 - `__dirname is not defined` when generating PrismaClient to custom location, w/ SvelteKit #15614 - Support for Cloudflare's new SQLite database D1 #13310 … - `@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 … **Issues addressed by Driver Adapters** - Using Prisma `NextJS` edge runtime leads to error #18763 - Set default values for schema `url` fields #222 **Issues addressed by promoting `schemaFolder` to GA** - Support for splitting Prisma schema into multiple files #2377 - bug(cli): `prisma format` does not format files other than `schema.prisma` when using `prismaSchemaFolder` preview feature #25136 - Feature: Remote schema #1563 … - 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 … I agree, I find the lack of pg_vector support very serious as well. Raw Queries and typed sql do not really help here, because you then give up a lot of prisma's DX. Ideally prisma would not only allow you to declare Unsupported- db types in the schema (as it already allows you to do), but it would also provide a way to influence the query that is generated if you use such a type in the query.