Skip to content

Commit c12b07b

Browse files
Merge pull request #1 from saisharan0103/codex/fix-documentation-for-prismaextension-configuration
docs: clarify prismaExtension usage
2 parents aaf40c3 + 296eb99 commit c12b07b

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/config/extensions/prismaExtension.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ If you are using Prisma, you should use the prisma build extension.
1212
- Support for TypedSQL and multiple schema files
1313
- You can use `prismaSchemaFolder` to specify just the directory containing your schema file, instead of the full path
1414
- You can add the extension twice if you have multiple separate schemas in the same project (example below)
15+
- `schema` must be a path to your `*.prisma` file, not just the folder containing it
16+
- When using multiple Prisma generators, use `clientGenerator` to point to the generator ID of the `prisma-client-js` generator
1517

1618
You can use it for a simple Prisma setup like this:
1719

@@ -63,7 +65,7 @@ export default defineConfig({
6365

6466
### clientGenerator
6567

66-
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.
68+
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.
6769

6870
<CodeGroup>
6971

@@ -155,3 +157,10 @@ prismaExtension({
155157
migrate: false,
156158
}),
157159
```
160+
161+
## Troubleshooting & Common Pitfalls
162+
163+
- **"Prisma Client could not locate the Query Engine for runtime 'debian-openssl-3.0.x'"**
164+
165+
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.
166+

0 commit comments

Comments
 (0)