chore(deps): bump @prisma/client from 5.8.0 to 5.9.1

[dependabot[bot]]

Bumps @prisma/client from 5.8.0 to 5.9.1.

Release notes

Sourced from @​prisma/client's releases.

5.9.1

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](prisma/prisma#22903)
• [v5.9.0 / Don't generate type. And the error from the previous version is still there #22896](prisma/prisma#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](prisma/prisma#22893)
• [Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22889](prisma/prisma#22889)
• [[5.9.0] All queries result in any type #22888](prisma/prisma#22888)
• [Prisma edge runtime error #22886](prisma/prisma#22886)
• [please how i cant fix this message issues #22885](prisma/prisma#22885)
• [[v5.9.0] $extends always return any #22884](prisma/prisma#22884)
• [[5.9.0] @​prisma/client in Next.js middleware #22877](prisma/prisma#22877)
• [Error after Upgrading from 5.8.1 to 5.9.0 #22875](prisma/prisma#22875)
• [[5.9.0 Bug] Prisma.TransactionClient appears to be missing types #22870](prisma/prisma#22870)

Note: many issues are duplicates.

5.9.0

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

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

This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:

• Improve the performance of relation queries by introducing JOINs (see last release).
• Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our survey).

Highlights

Optimized result sets for more efficient queries

We continue our efforts of the performance of Prisma Client queries. In 5.1.0, we introduced the RETURNING keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of RETURNING to SQLite and a broader range of queries for existing databases (e.g. delete on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:

• feat(qe): avoid extra select on delete queries
• feat(qe): enable queries with returning for sqlite

SQL Server: Return proper error for unreachable database

When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct P1001 error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.

Fixes and improvements

Prisma Client

... (truncated)

Commits

• 04b508b test(e2e): add new PrismaClient() in edge & mention Middleware in error (#2...
• 022fae4 fix(client): exports map (#22880)
• 469dc01 fix(client): Fix moduleResolution=Node16,NodeNext or Bundler (#22876)
• a4400c9 test(driver-adapters): add test for Bytes (#22810)
• b5bf6cf chore(deps): update dependency @​codspeed/benchmark.js-plugin to v3.1.0 (#22860)
• c459009 test(client): fix e2e flakiness (#22856)
• fca0b6d chore(deps): update engines to 5.9.0-32.23fdc5965b1e05fc54e5f26ed3de66776b93d...
• d766850 fix(cli, client): deletion of engines when --no-engine is passed (#22832)
• 60c02d2 fix(client): Fix $type key nested in JSON column (#22850)
• 850ed36 chore(deps): update engines to 5.9.0-31.dbcc905f0ab8f338d47bd9fe6323baffd45ed...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 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)