Sourced from prisma's releases.

6.12.0

Today, we are excited to share the 6.12.0 stable release 🎉

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ESM-compatible prisma-client generator now in Preview

We’re excited to share that our new and more flexible prisma-client generator is moving into Preview! As a reminder, here’s what it looks like:

generator client {
  // Required
  provider = "prisma-client" // no `-js` at the end!
  output   = "../src/generated/prisma"
// Optional

runtime                = "nodejs"

moduleFormat           = "esm"

generatedFileExtension = "ts"

importFileExtension    = "ts"

}

This new generator eliminates any headaches that you may have experienced due to magical code generation into node_modules and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!

Note: The prisma-client generator will become the default in Prisma v7, replacing the current prisma-client-js generator.

In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:

• React Router + Vite + Cloudflare
• React Router + Vite + Node.js
• Nuxt 3 + Vite + Nitro
• Deno Deploy

📚 Learn more in the docs.

Specify views and migrations folder locations in prisma.config.ts (Early Access)

As we’re getting closer to the General Availability release of prisma.config.ts, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations and views) to give you more flexibility and clarity on how to locate these files:

// prisma.config.ts
export default defineConfig({
  earlyAccess: true,
  migrations: {
    path: './db/migrations'
  },
  views: {
</tr></table> 

... (truncated)

• 9e35c80 fix(cli): always return valid JSON from MCP server (#27576)
• 0345aa9 fix: copy wasm files to output path in prisma-client generator (#27623)
• 4b4215f feat(config): add support for custom path for migrations, views, `typed...
• 0eab160 feat(config): lift "config.migrate.adapter" into "config.adapter" (#27618)
• cbb9810 chore(deps-dev): bump esbuild from 0.25.1 to 0.25.5 (#27581)
• 1ea2d4e chore(cli): update mcp sdk dependency (#27551)
• 8efbdc5 docs: add reference to MCP server repo (#27501)
• 86dc695 feat(tracking): ORM-1125 only track known top level commands (#27464)
• 604e937 test(cli): fix version snapshot with custom WASM components (#27444)
• 42166a0 feat: add RunnableContext object as additional arg passed to dynamic subcomma...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)