build(deps): bump @prisma/client from 4.12.0 to 4.14.1

Created by: dependabot[bot]

Bumps @prisma/client from 4.12.0 to 4.14.1.

Release notes

Sourced from @​prisma/client's releases.

4.14.1

Today, we are issuing the 4.14.1 patch release.

Fix in Prisma Client

• @​prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"

4.14.0

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

Request for feedback for Preview features

We would appreciate your feedback on a handful of Preview features to help us move them to General Availability soon. The Preview features include:

• PostgreSQL extensions
• Extended where unique
• Field reference support
• Order by Nulls
• Count by filtered relation

You can test them by enabling the Preview feature in your Prisma schema and giving them a try already in your Prisma schema, e.g., PostgreSQL extensions, or regenerating Prisma Client and trying them in your queries.

Highlights

Improved Prisma Client startup performance

For the last couple of months, we've been working hard to improve the performance of Prisma Client. We also published a blog post on how How We Sped Up Serverless Cold Starts with Prisma by 9x, which we recommend you give it a read.

This release continues with the same theme by making the size of the generated Prisma Client smaller. We have roughly halved the size of Prisma Client's dependencies.

More Introspection warnings for unsupported features

In 4.13.0, we introduced the first 6 introspection warnings that surface the existence of these features in your database and link to our documentation on how to manually work around the Prisma Schema with unsupported database features.

In this release, we added 3 more introspection warnings for the following features:

• Check Constraints (MySQL + PostgreSQL)
• Exclusion Constraints
• MongoDB $jsonSchema

On introspecting a database using any of these features, you will get a warning from the Prisma CLI and a comment in your Prisma schema where the feature is being used. The warning will also contain a link to instructions on how to manually use the feature.

Fixes and improvements

Prisma Client

• Generator output client leads to Error: ENOENT: no such file or directory, open '.../node_modules/@prisma/client/schema.prisma'
• DeprecationWarning: Implicit coercion to integer for exit code is deprecated
• thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: No unsupported field should reach that path', query-engine\connectors\sql-query-connector\src\model_extensions\scalar_field.rs:70:44
• jsonProtocol: in argument of filter types does not accept scalars

... (truncated)

Commits

• c4c1ada chore: Change shortlink for bundler-investigation on error case (#19247)
• c766261 fix(client): remove "os" import in ExitHooks, replacing it with a static map ...
• e1c26c1 chore(deps): update engines to 4.14.0-67.d9a4c5988f480fa576d43970d5a23641aa77...
• fffbd79 chore(deps): update engines to 4.14.0-66.20385323b6a30937c33354d7a9f7aeaff981...
• 29dc956 chore(deps): update engines to 4.14.0-65.b941a1de6ceb719196a59b0e60dcbd00ad51...
• 5a0f107 perf(esbuild): don't keep names during minification (#19095)
• 01626da chore(deps): update engines to 4.14.0-64.c694003bd22d0140d0f7911d1ddbdc9d7394...
• 637ab0c chore(deps): update engines to 4.14.0-63.bd111dfeac7de75d9ee9831f1b80ddf35f4e...
• 6838e4f chore(deps): update engines to 4.14.0-62.92998a9c18a9f9dbf25ba3f6ba7b1bb784c6...
• 0339b08 chore(deps): update engines to 4.14.0-58.c03b6915b9eff57212a16840d554da5f6f44...
• 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)