Bump prisma from 6.5.0 to 6.6.0

Bumps prisma from 6.5.0 to 6.6.0.

Release notes

Sourced from prisma's releases.

6.6.0

Today, we are excited to share the 6.6.0 stable release 🎉 This version comes packed with exciting features, we can't wait to see what you're going to build with it!

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

ESM support with more flexible prisma-client generator (Early Access)

We are excited to introduce a new prisma-client generator that's more flexible, comes with ESM support and removes any magic behaviours that may cause friction with the current prisma-client-js generator.

Note: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.

Here are the main differences:

  • Requires an output path; no “magic” generation into node_modules any more
  • Supports ESM and CommonJS via the moduleFormat field
  • Outputs plain TypeScript that's bundled just like the rest of your application code

Here's how you can use the new prisma-client generator in your Prisma schema:

// prisma/schema.prisma
generator client {
  provider     = "prisma-client"           // no `-js` at the end
  output       = "../src/generated/prisma" // `output` is required
  moduleFormat = "esm"                     // or `"cjs"` for CommonJS
}

In your application, you can then import the PrismaClient constructor (and anything else) from the generated folder:

// src/index.ts
import { PrismaClient } from './generated/prisma/client'

⚠️ Important: We recommend that you add the output path to .gitignore so that the query engine that's part of the generated Prisma Client is kept out of version control:

# .gitignore
./src/generated/prisma

📚 Learn more in the docs.

Cloudflare D1 & Turso/LibSQL migrations (Early Access)

Cloudflare D1 and Turso are popular database providers that are both based on SQLite. While you can query them using the respective driver adapter for D1 or Turso, previous versions of Prisma ORM weren't able to make schema changes against these databases.

... (truncated)

Commits
  • c2b06af feat(cli): add MCP server (#26700)
  • fab0649 feat(migrate): introduce @prisma/schema-engine-wasm and SchemaEngineWasm ...
  • 9764ec7 feat(config): map migrate.adapter and studio.adapter types (#26781)
  • 3de6206 chore(cli): move policy to top-level + rename (#26676)
  • d7ce546 chore(deps): bump esbuild from 0.24.2 to 0.25.1 (#26702)
  • 623fadd refactor: move generator out of client (#26678)
  • 403f21f fix(cli): don't use readConfigFile from typescript package (#26698)
  • edf34c6 refactor(schema folder): ORM 667 final cleanups (#26677)
  • e613ce9 fix(studio): ORM-666 use studio with schema folder fix (#26687)
  • 73af33f feat(schema folder): ORM 665 rework schema finding logic (#26663)
  • Additional commits viewable in compare view


Dependabot commands
You can trigger Dependabot actions by commenting on this MR
  • $dependabot recreate will recreate this MR rewriting all the manual changes and resolving conflicts

Merge request reports

Loading