build(dev-deps): bump @prisma/client from 5.9.0 to 5.9.1

[dependabot[bot]]

Bumps @prisma/client from 5.9.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.

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)
• See full diff 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)

[github-actions[bot]]

:tada: This PR is included in version 5.1.2 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: