Prisma 6.7.0 — Release Notes & Engineering Impact

Today, we are excited to share the `6.7.0` stable release 🎉  🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v6.7.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.7.0) about the release.** ## Highlights ### Prisma ORM without Rust engines (Early Access) If you're a regular visitor of our company blog, you may already know that we're currently working on moving the core of Prisma from Rust to TypeScript. We have written extensively about [why we're moving away from Rust](https://www.prisma.io/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm) and already shared [the first measurements of performance boosts](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance) we saw from the re-write. This re-write is not just a move from one programming language to another. It fundamentally improves the architecture of Prisma ORM and replaces the Query Engine (which is written in Rust and deployed as a standalone binary) with a much leaner and more efficient approach that we call _Query Compiler_. In this release, we're excited to give you [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) to the new Query Compiler for PostgreSQL and SQLite database 🥳 Support for more database will follow very soon! To use the new "Rust-free" version of Prisma ORM, add the `queryCompiler` (_new_) and `driverAdapters` feature flags to your client generator: ```prisma generator client { provider = "prisma-client-js" previewFeatures = ["queryCompiler", "driverAdapters"] output = "../generated/prisma" } ``` Now run `prisma generate` to re-generate Prisma Client. If you didn't use a [driver adapter](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) before, you'll need to install one. For example, the one for PostgreSQL: ``` npm install @prisma/adapter-pg ``` Once installed, you can instantiate `PrismaClient` as follows: ```ts import { PrismaPg } from '@prisma/adapter-pg' import { PrismaClient } from './generated/prisma' const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapter }) ``` This version of `PrismaClient` doesn't have a Query Engine binary and you can use it in the exact same way as before. 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine). ### Support for `better-sqlite3` JavaScript driver (Preview) [Driver adapters](https://www.prisma.io/docs/orm/overview/databases/database-drivers) are Prisma ORM's way of letting you use JS-native drivers (like [`pg`](https://node-postgres.com/)) to interact with your database. In this release, we're introducing a new driver adapter for using the [`better-sqlite3`](https://github.com/WiseLibs/better-sqlite3) package, so you can now interact with SQLite database in a JS-native way. To use it, first enable the `driverAdapters` Preview feature flag in on your client `generator`, then install these libraries: ``` npm install @prisma/adapter-better-sqlite3 ``` Now you can instantiate Prisma Client as follows: ```ts import { PrismaBetterSQLite3 } from '@prisma/adapter-better-sqlite3'; import { PrismaClient } from './generated/prisma'; const adapter = new PrismaBetterSQLite3({ url: "file:./prisma/dev.db" }); const prisma = new PrismaClient({ adapter }); ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/overview/databases/sqlite#using-the-better-sqlite3-driver). ### Multi-file Prisma schemas are now production-ready The `prismaSchemaFolder` Preview feature is moving into General Availability 🎉 With that change, Prisma ORM now by default supports splitting your Prisma schema file and e.g. lets you organize your schema as follows: **`prisma/schema.prisma`** → defines data source and generator ```prisma datasource db { provider = "postgresql" url = env("DATABASE_URL") } generator client { provider = "prisma-client-js" } ``` **`prisma/models/posts.prisma`** → defines `Post` model ```prisma model Post { id Int @id @default(autoincrement()) title String content String? published Boolean @default(false) author User? @relation(fields: [authorId], references: [id]) authorId Int? } ``` **`prisma/models/users.prisma`** → defines `User` model ```prisma model User { id Int @id @default(autoincrement()) email String @unique name String? posts Post[] } ``` ⚠️ Note that there have been [breaking changes to the `prismaSchemaFolder` Preview feature in the last 6.6.0 release](https://github.com/prisma/prisma/releases/tag/6.6.0). If you've been using this feature to split your Prisma schema, make sure to read the release notes and update your project accordingly. 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-schema/overview/location#multi-file-prisma-schema). ### Splitting generated output with new `prisma-client` generator (Preview) With the `prisma-client-js` generator, the generated Prisma Client library is put into a single `index.d.ts` file. This sometimes led to [issues](https://github.com/prisma/prisma/issues/4807) with large schemas where the size of the generated output could slow down code editors and breaking auto-complete. As of this release, our new `prisma-client` generator (that was released in [6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0)) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file. Also: As a bonus, we now ensure that generated files do not raise any ESLint and TypeScript errors! **Before** ``` generated/ └── prisma ├── client.ts ├── index.ts # -> this is split into multiple files in 6.7.0 └── libquery_engine-darwin.dylib.node ``` **After** ``` generated/ └── prisma ├── client.ts ├── commonInputTypes.ts ├── enums.ts ├── index.ts ├── internal │ ├── class.ts │ └── prismaNamespace.ts ├── libquery_engine-darwin.dylib.node ├── models │ ├── Post.ts │ └── User.ts └── models.ts ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#output-splitting-and-importing-types). ## Company news Our team has been busy shipping more than just the ORM! Check out these articles to learn what else we've been up to recently: - [Announcing: Prisma Postgres Integration for Vercel Marketplace](https://www.prisma.io/blog/connect-your-apps-to-prisma-postgres-via-vercel-marketplace-integration) - [Securely Access Prisma Postgres from the Frontend (Early Access)](https://www.prisma.io/blog/securely-access-prisma-postgres-from-the-frontend-early-access) - [Announcing Prisma's MCP Server: Vibe Code with Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres)