Update prisma monorepo to v4.16.2 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	4.6.1 -> 4.16.2
prisma (source)	4.6.1 -> 4.16.2

---

Release Notes

prisma/prisma (@​prisma/client)

v4.16.2

Compare Source

Today, we are issuing the 4.16.2 patch release.

Fixes in Prisma Client

• 4.16: (MongoDB) Generated types for list composites are incorrect
• Getting wrong types with prisma client extensions
• Prisma Client fluent API does not work with extends anymore on 4.16.1
• Prisma Client Extensions: $allModels: { $allOperations } sets query type to never
• Result types are incorrectly inferred when undefined explicitly passed to select/include

v4.16.1

Compare Source

Today, we are issuing the 4.16.1 patch release.

Fixes in Prisma Client

• Field references are not available on extended clients
• 4.16.x cannot wrap $extend in factory function when compilerOptions.composite is true
• Prisma Schema Type inside a Type not generating a right Payload
• Query in findMany in prisma extends returns a wrong type
• 4.16.0 Count query is not returning the right type when in a transaction
• FindMany returns wrong type after extending prisma client
• Can't specify $queryRawUnsafe return type after extending prisma client

v4.16.0

Compare Source

🌟 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 */
      }
    }
  })

• Prisma.validator can now also be used for extended types:

  const prisma = new PrismaClient().$extends({/* ... */})
  const data = Prisma.validator(prisma, 'user', 'findFirst', 'select')({
    id: true,
  })

• query callbacks for $queryRaw and $executeRaw will always receive Sql instance as args. This instance can be used to compose a new query using Prisma.sql:

  const prisma = new PrismaClient().$extends({
    query: {
      $queryRaw({ args, query }) {
        return query(Prisma.sql`START TRANSACTION; ${args}; COMMIT;`)
      }
    }
  })

• $on cannot be called after extending Prisma Client. Therefore, if you want to use event handlers together with extensions, we recommend using the $on method before $extends.

  const prisma = new PrismaClient()
    .$on(/* ... */)
    .$extends({/* ... */})

• We updated the import path for utilities used for authoring extension to @prisma/client/extension rather than @prisma/client

  + import { Prisma } from "@​prisma/client/extension"
  - import { Prisma } from "@​prisma/client"

Deprecating Middleware

We also took this opportunity to deprecate Prisma Client’s middleware. We recommend using to using Prisma Client query extension components which can be used to achieve the same functionality and with better type safety.

🚧 Middleware will still be available in Prisma Client’s API. However, we recommend using Prisma Client extensions over middleware.

Ordering by nulls first and last is now Generally Available

Starting with this release, we’re excited to announce that orderByNulls is now Generally Available! This means you can use the feature without the orderByNulls Preview feature flag.🌟

We introduced this feature in 4.1.0 to enable you to sort records with null fields to either appear at the beginning or end of the result.

The following example query sorts posts by updatedAt, with records having a null value at the end of the list:

await prisma.post.findMany({
  orderBy: {
    updatedAt: { sort: 'asc', nulls: 'last' },
  },
})

To learn more about this feature, refer to our documentation.

We’re excited to see what you will build! Feel free to share with us what you build on Twitter, Slack, or Discord.

Count by filtered relation is now Generally Available

This release moves the filteredRelationCount Preview feature to General Availability! This means you can use the feature without the filteredRelationCount Preview feature flag.

We first introduced this feature in 4.3.0 to add the ability to count by filtered relations.

The following query, for example, counts all posts with the title “Hello!”:

await prisma.user.findMany({
  select: {
    _count: {
      select: {
        posts: { where: { title: 'Hello!' } },
      },
    },
  },
})

To learn more about this feature, refer to our documentation.

Introspection warnings for expression indexes

In the last two releases, 4.13.0 and 4.14.0, we added 9 introspection warnings. These warnings surface features in use in your database that cannot currently be represented in the Prisma schema.

In this release, we’re adding one more introspection warning to the list: expression indexes.

On database introspection, the Prisma CLI will surface the feature with a warning, and a comment in your Prisma schema for sections for each feature in use. The warnings will also contain instructions for workarounds on how to use the feature.

Fixes and improvements

Prisma Client

• Attach comments to enum values
• Extend Prisma Client
• Triple-slash Comments should attach to Composite Types
• Nested disconnect fails on MongoDB with extendedWhereUnique
• [ClientExtensions, TypeScript] Fields of custom type aren't available when using the ClientExtensions preview-feature, unless select'd explicitly.
• Extensions incorrect typings generated (casing)
• Misleading error message of prisma generate when running it directly after installing prisma
• Prisma.validator: with clientExtensions enabled, Typescript can no longer compute types
• enum docstrings do not make it to the prisma client
• VScode behavior is very slow while using clientExtensions
• Client extensions in interactive transactions are bound to the base client
• $runCommandRaw is not passing the expected data to middleware or client extension
• PCE: Improve runtime types in raw query extensions
• Sequential transactions run out of order when using client extensions and middleware
• Client Extension: Make .prismaVersion.client available on "@​prisma/client/scripts/default-index"
• Cannot create record with Prisma.DbNull when clientExtensions enabled
• Extended client raw queries fail when using the Prisma.sql helper
• jsonProtocol: array shortcut is missing for distinct field
• Prisma Client Extension: support Prisma.validator
• Prisma Client: make clientExtensions GA
• PCE: Query extensions of $queryRawUnsafe also triggers $allModels.$allOperations
• PCE: $on applied to an extended client is also bound to the parent client
• Type "never" returned from nested properties when using "select" after enabling data proxy + accelerate
• $queryRaw* is broken in interactive transactions together with clientExtensions in 4.16.0-dev.17
• Deploying to an offline environment fails because it tries to download a Prisma engine checksum file
• jsonProtocol: Wrong error message shown for validation error for checked/unchecked types
• Bug: FindXOrThrow don't get batched on the engine

Prisma Migrate

• Allow skipping sha checksum
• Documentation not available in DMMF for MongoDB types
• prisma db pull gets rid of @default(uuid()) on re-introspection

Language tools (e.g. VS Code)

• Go to Definition does not work when target model contains a field with a type name that starts with the same name

Prisma Studio

• Error: spawn xdg-open ENOENT on prisma studio

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 22 at 5 pm Berlin | 8 am San Francisco.

v4.15.0

Compare Source

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

Highlights

For this release, we focused on fixing bugs and making smaller quality-of-life improvements.

Support for custom arguments for prisma db seed

This release adds support for defining and passing arbitrary arguments to prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to the prisma db seed command. A few example use-cases include, but are not limited to:

• Seeding different data in different environments
• Partially seeding data in some tables

Here is an example seed.ts file that defines custom arguments for seeding different data in different environments:

// prisma/seed.ts
import { parseArgs } from "node:util";

const options = {
  environment: { type: 'string', },
}

async function main() {
  const { values: { environment } } = parseArgs({ options })
  
  switch (environment) {
    case "development":
      /** do something for development */
      break;
    case "test":
      /** do something  for test  environment */
      break;
    default:
      break;
  }
}

main()

You can then provide the environment argument when executing the seed script as follows:

npx prisma db seed -- --environment development

Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.

Improved error messages when Query Engine file is not found

This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:

• The downloaded Query Engine doesn’t match the runtime/ target platform your application is running on.
• The Query Engine is not copied to your final application bundle during the build step.

We hope these error messages are helpful while debugging your application.

Prisma VS Code extension improvements

In this release, we made a few improvements to our VS Code extension:

1. Updated the file system watcher that is responsible for restarting the TypeScript server when prisma generate is run to ensure the types are in sync

   Note:

   • This new approach is currently only available on Windows and Linux. We plan on adding support for the new file system watcher on macOS soon.
   • This requires both Prisma CLI & VS code extension version 4.15.0 or higher

2. Added Quick Fixes action for unique identifiers for MongoDB to add the @map("_id") attribute function when it’s missing on an identifier field

   Screen.Recording.2023-05-17.at.19.22.20.mov

3. Support for renaming symbols for composite types and views

   type-symbol-rename.mov

Fixes and improvements

Prisma Client

• Prisma generate - Error: write EPIPE on WSL <-> Windows
• prisma generate is blocked by query-engine-rhel-openssl-1.0.x opening in Notepad on Windows
• Generated client output path hardcoded to build environment
• Issue with Yarn Workspace Monorepo: Query engine binary for current platform could not be found.
• Cloning a project with checked in node_modules (from another platform) leads to platform engine not being present
• SvelteKit, Vite and Prisma "module not defined"
• Schema File Not Found in non monorepo with custom output
• Deploying to Cloudflare Workers | "PrismaClient is unable to be run in the browser"
• Inline/bundle the contents of the prisma schema on generate
• Netlify: Query engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.x
• Query Engine Library Not Found
• No client schema when using PrismaClient during cached (standard) Netlify build
• Module "@​prisma/client" has no exported member "PrismaClient"
• EPERM: operation not permitted
• prisma/client crashes when used with older versions of react-refresh
• Unable to run prisma cli in pnpm monorepo from workspace install
• Misleading error message when the query engine is not found
• When setting custom client output directory, generated package.json does not include "sideEffects: false"
• You already added the platform "debian-openssl-1.1.x" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong.
• Prisma seems to be looking in the wrong location for rhel-openssl-1.0.x
• Can't find prisma engine
• Cannot find name '$PrismaModel' due to feature extendedWhereUnique with preview feature fieldReference
• Netlify build fails with PrismaClientInitializationError
• i'm getting the error while requesting the api
• Query engine library for current platform could not be found.
• Prisma unable to reconnect if initial connection fails
• GraphQL protocol encoder incorrectly turns empty array into empty object.
• GraphQL protocol: Invalid Date values silently turn into nulls
• @​prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"
• Client is bricked from connecting to DB if first attempt fails.
• JSON protocol: incorrect recursive composites detection through multiple nesting levels
• fieldReference is not working with enums

Prisma Migrate

• Pass extra arguments to prisma db seed to the seed command
• Typo in generating migration SQL to add enum.

Language tools (e.g. VS Code)

• MongoDB: Quick fix for missing @map("_id") annotation
• Rename composite types
• Views: Support for rename
• TextDocument deprecation
• Lib name change vsce -> @​vscode/vsce

Credits

Huge thanks to @​RobertCraigie, @​KhooHaoYit, @​art049, @​luxaritas, @​mrazauskas, @​maxmartynov, @​haneenmahd for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 1 at 5 pm Berlin | 8 am San Francisco.

v4.14.1

Compare Source

Today, we are issuing the 4.14.1 patch release.

Fix in Prisma Client

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

v4.14.0

Compare Source

🌟 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
• jsonProtocol should report errors as nicely as before
• Generated client with custom path containing string client: ENOENT: no such file or directory, open 'D:\<projectpath>\node_modules\.prisma\client\schema.prisma
• Can't find the schema when the project path contains the same name as the generated client folder

Prisma Migrate

• Build all glibc Linux binaries with CentOS 7
• Remove Please create an issue ... in MigrateEngine.ts
• Do not introspect exclusion constraints as Gist indexes
• Introspection warnings: move rendering from DbPull.ts to the engine
• views: don't create local views folder on introspection if no views are found
• RelationMode autocomplete uses incorrect casing

Language tools (e.g. VS Code)

• Support for VSCode Region Marker Folding

Credits

Huge thanks to @​RobertCraigie, @​KhooHaoYit, @​art049, @​luxaritas, @​mrazauskas for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, May 11 at 5 pm Berlin | 8 am San Francisco.

v4.13.0

Compare Source

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

Highlights

Introspection warnings for unsupported features

The Prisma Schema Language (PSL) currently doesn't support all database features and functionality of our target databases. The PSL is an abstraction over SQL and will keep evolving to address gaps in our database feature matrix.

Before this release, prisma db pull did not pick up the unsupported features in a database. It was easy to lose them when running prisma migrate dev based on an existing Prisma schema if not included in a migration file using custom migrations.

To avoid this, we added 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 introspection warnings for the following features:

• Partitioned tables
• PostgreSQL Row Level Security
• Index sort order, NULLS FIRST / NULLS LAST
• CockroachDB row-level TTL
• Comments
• PostgreSQL deferred constraints

Prisma CLI will output warnings on introspection (prisma db pull) and add comments to your Prisma schema. In the coming releases, we will expand this to many more features labeled with topic: database-functionality on GitHub.

Improved support for Netlify and Vercel build process

Netlify and Vercel cache project dependencies during the build process and reuse that cache until dependencies change. While this helps speed up the build process, any postinstall scripts of these dependencies will not be executed.

Prisma uses a postinstall script in its package to automatically trigger the customized generation of Prisma Client for your Prisma Schema. When a dependency cache is used, that generation process is not triggered, and an outdated Prisma Client may be used in your application.

When you update your Prisma Schema but not your dependencies, Prisma Client will not be generated for the new schema. For example, columns you added recently to one of your models will not be present in the Prisma Client API - causing errors.

This problem can be avoided by:

1. Adding a custom postinstall script in your package.json file
2. Manually adding a prisma generate step to the “Build” scripts of Vercel and Netlify.

We now added detection of this scenario and will prevent a build without an additional prisma generate. This will ensure you're aware of the problem early and get guidance on how to fix this problem. You can read more on how to do this in our docs — Vercel caching troubleshooting, Netlify caching troubleshooting.

Better support for pnpm as a package manager

Before this release, Prisma only used npm scripts which would lead to undesirable behavior for a project using a different package manager such as pnpm and yarn. This release improves the detection of the package managers in your project by using ni. If you're still running into this problem, let us know by creating a GitHub issue.

Segmentation fault and TLS connection error fix

In this release, we've fixed a TLS connection error segmentation fault. This mostly affected users running on Node.js 17 or later with OpenSSL 1.1 when using TLS to connect to their database.

JSON protocol Preview feature feedback

We have fixed multiple bugs for the jsonProtocol Preview feature and are close to making it Generally Available. We are still looking for feedback about its usage to ensure it is ready and works as expected for everyone.

We would appreciate it if you would try it out, help us polish the feature, and move it to General Availability. Testing it requires little effort. You can test it using the following steps:

1. Enabling the jsonProtocol Preview feature in your Prisma schema
2. Re-generating Prisma Client
3. Running your application or tests to make sure everything works

We encourage you to leave your feedback in this GitHub issue or create a bug report if your run into any issues.

Fixes and improvements

Prisma Client

• prisma generate fails when using pnpm workspaces because it tries to install prisma dependencies with npm or yarn
• Netlify deploy does not pick up changes to schema file
• Vercel: Schema only change does not invalidate build cache
• Serverless deployments: Just making a schema level change to a repository does not invalidate node_modules cache that contains generated Client
• pnpm: Can not prisma generate when @prisma/client is not installed in project
• Segmentation fault crash when using prisma client when using PostgreSQL
• Docker with pnpm install hangs on @prisma/client postinstall
• Automatic installation of missing dependencies isn't compatible with pnpm
• Prisma generate throws dependency error karma-chai
• Postinstall script fails with PNPM workspaces due to npm ERR! Cannot read properties of null (reading 'matches')
• Debian 11 Node 19.3.0 segmentation fault
• Prisma client segfault on Ubuntu 22.04
• Segmentation Fault in Postgres
• Using Prisma with pnpm results in inability to call database related commands
• Prisma Connect Causes NodeJS to Close With Exit Code 0
• 99056 segmentation fault (core dumped) node --require esbuild-register prisma/seed.ts
• JSON protocol: sibling composites of the same type are rejected

Prisma Migrate

• prisma db pull adds redundant comments: "This table is a partition table ..."
• Render warning code 30 in cli (PG RLS)

Language tools (e.g. VS Code)

• [object Object] output in logging isn't helpful

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​maxmartynov, @​haneenmahd for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, April 20 at 5 pm Berlin | 8 am San Francisco.

v4.12.0

Compare Source

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

Highlights

Introspection of Views SQL improvements (Preview)

The views Preview feature significantly improved this release: prisma db pull now reads the SQL query used to define a view and stores it in a .sql file in a views folder next to your Prisma schema.

Note: These .sql files are not yet used for creating or updating views during migrations yet. For now, we are only looking for feedback. Let us know if the introspected SQL files match the views picked up in your database and if the correct files were created in your filesystem.

We encourage you to leave feedback in this GitHub issue.

Improvements to JSON protocol (Early Preview)

In 4.11.0, we announced the jsonProtocol Preview feature which had some rough edges. This release improves the Preview feature by providing polished and helpful error messages from Prisma Client when something goes wrong. Here is an example error message:

We would appreciate it if you would try it out to help us polish the feature and move it to General Availability. Testing it requires little effort. Please also leave any feedback in this issue, or open a new one if you want to report a bug.

Prisma Client startup performance

In this release, we've improved the startup performance of Prisma Client. We're keen on improving the performance of Prisma Client. If you experience any problems with the startup performance, be sure to report them so that we can look into them.

Open Telemetry tracing and logging for Prisma Client for Data Proxy

This release adds support for Open Telemetry tracing (via the tracing Preview feature) and logging to Prisma Client for Data Proxy.

Fixes and improvements

Prisma Migrate

• Certain types of schema changes don't work with CockroachDB v22.2
• Completions: provided by engines break right at the start of a newline
• db pull fail with particular enum default value in column
• Unable to reset CockroachDB for table with foreign key relationship on v22.2.
• Introspection of SQLite views
• Changing the Column Type to Enum on a model throws an error
• Introspection of the view definition statement
• MySQL multi-value index removes the primary key on introspection

Prisma Client

• findUnique used with Promise.all returns null
• Missing PrismaPromise export after update from 4.9.0 to 4.11.0
• jsonProtocol doesn't query enum fields by default
• Prisma 4.11 breaks multilevel relation with compound primary keys (typings)
• 4.11.0: Unique constraint failed on the fields on query that worked in 4.10.1
• jsonProtocol Field/Enum is not included in the result of the findFirst/findMany function
• Too many records are returned in 4.11.0 when using nested include and @​unique field is null
• Objects with computed properties returned from an extended prisma client return true for any property name when calling hasOwn or hasOwnProperty on it

Language tools (e.g. VS Code)

• Completions: suggest type block for MongoDB
• Remove datasource completions

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​ivan, @​art049 for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, March 30 at 5 pm Berlin | 8 am San Francisco.

v4.11.0

Compare Source

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

Highlights

JSON protocol Early Preview

This release introduces an early Preview feature: JSON protocol.

During performance investigations and optimizations, we noticed that the existing implementation added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON.

To try out the new protocol, enable the jsonProtocol Preview feature in your Prisma schema:

generator client {
  provider        = "prisma-client-js"  
  previewFeatures = ["jsonProtocol"]
}

Regenerate Prisma Client to use the new JSON protocol.

For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: PRISMA_ENGINE_PROTOCOL=json.

Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases. Using it with Data Proxy and Prisma Data Platform currently also leads to errors.

We expect using jsonProtocol to improve Prisma Client's startup performance significantly. This will likely have a more significant impact on applications with larger Prisma schemas.

We would appreciate your feedback on this feature on the following particularly:

1. Does using this preview feature introduce any regressions or problems in your application?
2. If not, how does it influence the performance of your application? Can you share before and after measurements?

For feedback, please comment on the GitHub feedback issue.

Introspection support for MySQL, SQL Server, and CockroachDB views

You can now run prisma db pull against your database to populate your Prisma schema with your views in MySQL, SQL Server, and CockroachDB.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Prisma Client extensions improvements: raw query operations

This release adds support for extending top-level raw query operations.

const prisma = new PrismaClient().$extends({
  query: {
    // relational databases
    $queryRaw({ args, query, operation }) {
      // handle $queryRaw operation
      return query(args)
    },
    $executeRaw({ args, query, operation }) {
      // handle $executeRaw operation
      return query(args)
    },
    $queryRawUnsafe({ args, query, operation }) {
      // handle $queryRawUnsafe operation
      return query(args)
    },
    $executeRawUnsafe({ args, query, operation }) {
      // handle $executeRawUnsafe operation
      return query(args)
    },
    // MongoDB
    $runCommandRaw({ args, query, operation }) {
      // handle $runCommandRaw operation
      return query(args)
    },
  },
})

Webpack plugin for Next.js apps using Prisma in monorepo setups

If you've been using Prisma Client in a Next.js app in a monorepo setup, you might have seen this infamous error message:

Error: ENOENT: no such file or directory, open schema.prisma

We finally pinpointed the problem's source to the Next.js bundling step and opened an issue in the Next.js repository for Vercel to investigate and hopefully fix it.

In the meantime, we've created a workaround via a webpack plugin that makes sure your Prisma schema is copied to the correct location: @prisma/nextjs-monorepo-workaround-plugin.

To use the plugin, first install it:

npm install -D @​prisma/nextjs-monorepo-workaround-plugin

Import the plugin into your next.config.js file and use it in config.plugins:

const { PrismaPlugin } = require('@​prisma/nextjs-monorepo-workaround-plugin')
module.exports = {
  webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, new PrismaPlugin()]
    }
    return config
  },
}

For further information, refer to our documentation to learn how to use it and open an issue if it doesn't work as expected.

Fixes and improvements

Prisma Client

• Prisma hangs when javascript is minified
• Issue with prisma failing to locate schema file in monorepo
• NextJS try to open "schema.prisma" at wrong path.
• pnpm workspace + nextjs: ENOENT: no such file or directory, open '...\.next\server\pages\api\schema.prisma'
• next.js ENOENT trying to open schema.prisma
• Error with custom output in NPM monorepo: Error: ENOENT: no such file or directory, open 'schema.prisma'
• Error with custom output in Turborepo using Blitz.js: Error: ENOENT: no such file or directory, open '<...>/schema.prisma'
• Upsert fails on Postgres with list column.
• Error received when connecting items in an existing one-to-many relationship on MySQL
• ENOENT with custom output and ESM module in NPM monorepo (including Nextjs): no such file or directory, open /.../schema.prisma...
• Setting ignoreEnvVarErrors: true Node API QE causes datasourceOverrides to be ignored
• PCE: Support query extensions for raw queries

Prisma Migrate

• sslaccept=accept_invalid_certs not working with mysql server 8.0.30
• Error 08S01 (1043) -> Bad Handshake. MySQL Connection with SSL certs
• Introspection of MySQL views
• Introspection of SQL Server views
• Introspection of CockroachDB views
• db pull: add new codes for introspection warnings for views in the CLI
• Figure out where getDMMF is used for validation
• Error when directUrl is prisma:// connection string
• 4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.
• Validation output is now always colored, also in CI
• Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)
• Fix Postgres introspection of partition tables false positives on inherited tables
• Support openSUSE Tumbleweed
• Change validate to return Result<(), JsError> in Wasm module
• (internal): add unit tests for path-specific libssl version parsing

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​ivan, @​Mini256, @​Lioness100, @​yukukotani, @​sandrewTx08, @​fubhy, @​zachtil, @​unflxw, @​Mosaab-Emam for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, March 2 at 5 pm Berlin | 8 am San Francisco.

v4.10.1

Compare Source

Today, we are issuing the 4.10.1 patch release.

Fixes in Prisma Client

• Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)
• 4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.

v4.10.0

Compare Source

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

Highlights

Improved CLI support for connection poolers

When working with connection poolers such as the Prisma Data Proxy, Accelerate or [pgBouncer](https://www.prisma.io/docs/guides/performance-a

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.