Home / DEVTOOLS / Prisma / 5.9.1
Prisma 5.9.1stable Released Feb 01, 2024
Impact Score: 5/10

Prisma 5.9.1 — Release Notes & Engineering Impact

Source available — automated, not human-reviewed

Component: prisma · Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified — check source notes
$ npm install --save-dev --save-exact [email protected]
📄 .MD
🔧 Bug Fixes 6
⚡ Executive Summary (TL;DR)

Prisma 5.9.1. Source highlight: Today, we are issuing the `5.9.1` patch release.

Visit Prisma Official Site ↗ Official Release Source ↗ All Prisma Releases 📡 Prisma RSS
Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

📊 Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

⚙️ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

🔧 Bug Fixes & Patches (6)

  • [[5.9.0] Getting strange types after generating #22903](https://github.com/prisma/prisma/issues/22903)
  • v5.9.0 / Don't generate type. And the error from the previous version is still there #22896
  • [[5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22893](https://github.com/prisma/prisma/issues/22893)
  • `Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #22889
  • [[5.9.0] All queries result in any type #22888](https://github.com/prisma/prisma/issues/22888)
  • Prisma edge runtime error #22886
📄 View Raw Release Notes (Original Developer Log)
Today, we are issuing the `5.9.1` patch release. ## Fixes in Prisma Client In `5.9.0` we have changed our conditional exports in `@prisma/client`. This resulted in broken types for TypesScript users using certain combinations of `module`/`moduleResolution` settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side. You can now try out `5.9.1` and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report - [[5.9.0] Getting strange types after generating #22903](https://github.com/prisma/prisma/issues/22903) - [v5.9.0 / Don't generate type. And the error from the previous version is still there #22896](https://github.com/prisma/prisma/issues/22896) - [[5.9.0] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22893](https://github.com/prisma/prisma/issues/22893) - [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #22889](https://github.com/prisma/prisma/issues/22889) - [[5.9.0] All queries result in any type #22888](https://github.com/prisma/prisma/issues/22888) - [Prisma edge runtime error #22886](https://github.com/prisma/prisma/issues/22886) - [please how i cant fix this message issues #22885](https://github.com/prisma/prisma/issues/22885) - [[v5.9.0] $extends always return any #22884](https://github.com/prisma/prisma/issues/22884) - [[5.9.0] @prisma/client in Next.js middleware #22877](https://github.com/prisma/prisma/issues/22877) - [Error after Upgrading from 5.8.1 to 5.9.0 #22875](https://github.com/prisma/prisma/issues/22875) - [[5.9.0 Bug] Prisma.TransactionClient appears to be missing types #22870](https://github.com/prisma/prisma/issues/22870) Note: many issues are duplicates.
← Older Version Prisma 5.9.0