From 296eb997969b05510c06302f1460afe8b26a805e Mon Sep 17 00:00:00 2001 From: Domakonda SaiSharan <99661288+saisharan0103@users.noreply.github.com> Date: Wed, 25 Jun 2025 17:54:46 +0530 Subject: [PATCH 1/2] docs: clarify prismaExtension usage --- docs/config/extensions/prismaExtension.mdx | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/config/extensions/prismaExtension.mdx b/docs/config/extensions/prismaExtension.mdx index 73bc94b16a..dd2deae72f 100644 --- a/docs/config/extensions/prismaExtension.mdx +++ b/docs/config/extensions/prismaExtension.mdx @@ -12,6 +12,8 @@ If you are using Prisma, you should use the prisma build extension. - Support for TypedSQL and multiple schema files - You can use `prismaSchemaFolder` to specify just the directory containing your schema file, instead of the full path - You can add the extension twice if you have multiple separate schemas in the same project (example below) +- `schema` must be a path to your `*.prisma` file, not just the folder containing it +- When using multiple Prisma generators, use `clientGenerator` to point to the generator ID of the `prisma-client-js` generator You can use it for a simple Prisma setup like this: @@ -63,7 +65,7 @@ export default defineConfig({ ### clientGenerator -If you have multiple `generator` statements defined in your schema file, you can pass in the `clientGenerator` option to specify the `prisma-client-js` generator, which will prevent other generators from being generated. Some examples where you may need to do this include when using the `prisma-kysely` or `prisma-json-types-generator` generators. +If you have multiple `generator` statements defined in your schema file, you can pass in the `clientGenerator` option to specify the `prisma-client-js` generator, which will prevent other generators from being generated. Use the **generator ID** from your schema (for example `client`), not the provider name (`prisma-client-js`). Some examples where you may need to do this include when using the `prisma-kysely` or `prisma-json-types-generator` generators. @@ -155,3 +157,10 @@ prismaExtension({ migrate: false, }), ``` + +## Troubleshooting & Common Pitfalls + +- **"Prisma Client could not locate the Query Engine for runtime 'debian-openssl-3.0.x'"** + + This usually means the Prisma extension wasn't added to your `trigger.config.ts` file. Ensure that `prismaExtension()` is present in your `build.extensions` array. You don't need to download any Prisma binaries manually—Trigger will handle that for you. + From b29cf997c64a6cb9c3678c592c2eedf3d943fb2c Mon Sep 17 00:00:00 2001 From: Domakonda SaiSharan <99661288+saisharan0103@users.noreply.github.com> Date: Fri, 27 Jun 2025 14:00:07 +0530 Subject: [PATCH 2/2] Revert "docs: clarify prismaExtension usage" --- docs/config/extensions/prismaExtension.mdx | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/docs/config/extensions/prismaExtension.mdx b/docs/config/extensions/prismaExtension.mdx index dd2deae72f..73bc94b16a 100644 --- a/docs/config/extensions/prismaExtension.mdx +++ b/docs/config/extensions/prismaExtension.mdx @@ -12,8 +12,6 @@ If you are using Prisma, you should use the prisma build extension. - Support for TypedSQL and multiple schema files - You can use `prismaSchemaFolder` to specify just the directory containing your schema file, instead of the full path - You can add the extension twice if you have multiple separate schemas in the same project (example below) -- `schema` must be a path to your `*.prisma` file, not just the folder containing it -- When using multiple Prisma generators, use `clientGenerator` to point to the generator ID of the `prisma-client-js` generator You can use it for a simple Prisma setup like this: @@ -65,7 +63,7 @@ export default defineConfig({ ### clientGenerator -If you have multiple `generator` statements defined in your schema file, you can pass in the `clientGenerator` option to specify the `prisma-client-js` generator, which will prevent other generators from being generated. Use the **generator ID** from your schema (for example `client`), not the provider name (`prisma-client-js`). Some examples where you may need to do this include when using the `prisma-kysely` or `prisma-json-types-generator` generators. +If you have multiple `generator` statements defined in your schema file, you can pass in the `clientGenerator` option to specify the `prisma-client-js` generator, which will prevent other generators from being generated. Some examples where you may need to do this include when using the `prisma-kysely` or `prisma-json-types-generator` generators. @@ -157,10 +155,3 @@ prismaExtension({ migrate: false, }), ``` - -## Troubleshooting & Common Pitfalls - -- **"Prisma Client could not locate the Query Engine for runtime 'debian-openssl-3.0.x'"** - - This usually means the Prisma extension wasn't added to your `trigger.config.ts` file. Ensure that `prismaExtension()` is present in your `build.extensions` array. You don't need to download any Prisma binaries manually—Trigger will handle that for you. -