Bump @prisma/generator-helper from 3.14.0 to 3.15.0

[dependabot[bot]]

Bumps @prisma/generator-helper from 3.14.0 to 3.15.0.

Release notes

Sourced from @​prisma/generator-helper's releases.

3.15.0

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements

Improvements to Prisma Client for Data Proxy

In this release, we're shipping a couple of improvements to Prisma Client for Data Proxy.

The Prisma Data Proxy provides connection management and pooling for database connections for efficiently scaling database connections in serverless environments. The Prisma Client for Data Proxy provides support for connecting to the Prisma Data Proxy using HTTP.

We introduced this feature in version 3.3.0 and constantly shipped features, fixes, and improvements.

One of the changes in this release is improving the Prisma Client for the Data Proxy generation step.

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}
generator client {
provider        = "prisma-client-js"

previewFeatures = ["dataProxy"]
}

You can generate Prisma Client for the Data Proxy it by using the --data-proxy flag:

npx prisma generate --data-proxy

We also updated how you can run Prisma Client using the Data Proxy in Cloudflare Workers and Edge environments. You can now use @prisma/client/edge instead of @prisma/client in your application.

import { PrismaClient } from '@prisma/client/edge'

To learn more, check out our documentation.

Prisma Client Metrics is now in Preview

Metrics is a new Preview feature that allows you to monitor how Prisma Client interacts with your database. Metrics expose a set of counters, gauges, and histograms that can be labeled and piped into an external monitoring system like Prometheus or StatsD.

You can use metrics in your project to help diagnose how your application's number of idle and active connections changes with counters, gauges, and histograms.

To get started using metrics in your project, enable the Preview feature flag in your Prisma schema:

</tr></table> 

... (truncated)

Commits

• a7b02ca chore(client, cli): implement --data-proxy [DPGA, 1] (#13561)
• fbd24a3 chore(deps): update dependency @​types/jest to v28
• 4131eb2 chore: bump typescript (#13535)
• 24a1ec0 chore(deps): update jest
• 596a26f chore(deps): update devdependencies (non-major) (#13401)
• 1df2af3 chore(deps): update devdependencies (non-major) (#13303)
• 0f675e4 chore(CD): tweak Buildkite publish (#13151)
• 430fd7f chore(deps): update dependency @​swc/jest to v0.2.21 (#13281)
• a4e454c chore(deps): update definitelytyped
• 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 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)