chore(deps): bump @prisma/internals from 4.15.0 to 4.16.0

[dependabot]

Bumps @prisma/internals from 4.15.0 to 4.16.0.

Release notes

Sourced from @​prisma/internals's releases.

4.16.0

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

Highlights

This release promotes the following Preview features to General Availability:

• Prisma Client extensions
• Ordering by nulls first and last
• Count by filtered relation

Prisma Client extensions are Generally Available

Today, we’re very excited to announce that Prisma Client extensions are Generally Available and production-ready! This means you can use the feature without the clientExtensions Preview feature flag.🚀

Prisma Client extensions are a powerful new feature for adding functionality on top of your Prisma Client in a type-safe manner. With this feature, you can create simple, but flexible solutions.

Prisma Client extensions have 4 different types of components that can be included in an extension:

• Result extensions components: add custom fields and methods to query result objects, for example, virtual/computed fields.
• Model extensions components: enable you to add new methods to your models alongside existing model methods such as findMany.
• Query extensions components: let you hook into the lifecycle of a query and perform side effects, modify query arguments, or modify the results in a type-safe way. These are an alternative to middleware that provide complete type safety and can be applied in an ad-hoc manner to different extensions.
• Client extensions components: allow you to add new top-level methods to Prisma Client. You can use this to extend Prisma Client with functionality that isn’t tied to specific models.

const prisma = new PrismaClient().$extends({
  name: "extension-name",
  result: { /* ... */ },
  model: { /* ... */ },
  query: { /* ... */ },
  client: { /* ... */ },
});

You can also create and publish extensions for others to use. Learn more about how to share extensions in our documentation.

More features and changes made to Client Extensions

We also made the following improvements to Prisma Client extensions in preparation for General Availability:

• Added a top-level $allOperations method for query component that captures all model operations as well as top-level raw queries. Refer to our documentation for more information.

  const prisma = new PrismaClient().$extends({
    query: {
      $allOperations({ args, query, operation, model }) {
        /* your extension's logic here */
      }
    }

... (truncated)

Commits

• 4a547e7 fix: Fix error messages stating "Please install it with [object Promise]" (#1...
• d08e685 chore(deps): update engines to 4.16.0-66.b20ead4d3ab9e78ac112966e242ded703f4a...
• 955c0bb chore(deps): update engines to 4.16.0-60.b4faed7994b42a1ae3c96d243ab2410aaa8c...
• e2fcb9b chore(deps): update engines to 4.16.0-59.51d4d989d63f71c4e681a08ee47ad43f62ae...
• dd6089f chore(deps): update engines to 4.16.0-56.489dea78e5d64611960acfde15ac92fee3f2...
• f9b1705 fix(client): Improve union error ranking heuristics (#19711)
• 36a7ce1 feat(client): Integrate engine-side validation for model name in field refere...
• a49a6d3 chore(deps): update engines to 4.16.0-42.ffceeccf256b1d7b039c6ceed46fa24d8049...
• c9c5c0a chore(deps): update dependency @​types/jest to v29.5.2 (#19640)
• d5f79b6 chore(deps): update engines to 4.16.0-39.810585b970adb07a9de10de64be74f871a2a...
• 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 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)

[dependabot]

Superseded by #38.