Skip to content

📚 Fix Prisma Extension Docs for Common Misconfigurations (#2167) #2203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Revert "docs: clarify prismaExtension usage"
  • Loading branch information
saisharan0103 authored Jun 27, 2025
commit b29cf997c64a6cb9c3678c592c2eedf3d943fb2c
11 changes: 1 addition & 10 deletions docs/config/extensions/prismaExtension.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down Expand Up @@ -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.

<CodeGroup>

Expand Down Expand Up @@ -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.