3-Month Roadmap: September, October, November 2025

This quarter is one of the most significant in recent Prisma history — we’re preparing for **Prisma 7**, a major release that modernizes the ORM’s foundations and paves the way for the next generation of features. Alongside this, we’re expanding database capabilities with **PostgreSQL extensions**, shipping long-awaited polish by graduating preview features, and addressing one of the most common pain points for the community: **unstable generator APIs**. Our top five goals: ... Community-built generators have become a cornerstone of the Prisma ecosystem — but until now, they’ve relied on **internal, unstable APIs**, making them prone to breaking when Prisma versions change. This quarter, we’re introducing a **stable, versioned API for generators**. ... - prisma generate --sql does not read env vars in AWS #25512 - 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 ... - `@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 - prisma-client: package developers cannot import runtime objects #27707 - [6.7.0] Get a list of model fields without `Prisma.dmmf` #27028 - Cannot bundle new prisma-client with esbuild in cjs #28229 - Prisma ESM import breaks with import-in-the-middle (ERR_INVALID_RETURN_PROPERTY_VALUE) #28198 - mjs imports fail when using engineType = "client" #28130 - Getting Dynamic require of "node:path" is not supported for esbuild + Prisma 6.16.2 + prisma-client generator + engineType = "client" #28126 - Make `prisma-client` compatible with JavaScript without tsc #28116 - Possible WASM loading incompatibility with Vite #28105 - Generated prisma code after compiling with tsc gives errors #28104 - ./node_modules/@prisma/adapter-pg/dist/index.mjs [Client Component Browser] on the prisma without rust engine #28096 - The basic installation from the documentation (for Nuxt) does not run -- @prisma/client is **never** correctly loaded #26991 - PrismaClient is using index-browser.js during Node tests with Vitest + SWC + custom output directory #27627 - [prisma-client generator]: Split types and ModelName into their own files to support client/browser code #27341 … ## Activity wmaddenpinned this issue on Oct 11, 2025