The prismaExtension has been completely redesigned to support Prisma 7's new architecture, while maintaining full backward compatibility with Prisma 6.x. Whether you're using the traditional prisma-client-js provider or the new Rust-free client architecture, we've got you covered.
Three modes for every deployment strategy
Prisma is evolving fast. Version 7 introduces a fundamentally different client architecture, moving away from the traditional Rust-based engine (yay!). To support this transition we've rebuilt the extension around three distinct modes:
Legacy Mode (Prisma 6.x and earlier)
Use this when you're running Prisma 6.x or earlier with the standard prisma-client-js provider.
What's new:
- Fixes an issue with multi-file schema support
- Adds support schema location detection from
prisma.config.ts - Enhanced auto-version detection
import { prismaExtension } from "@trigger.dev/build/extensions/prisma";export default defineConfig({ project: "proj_your-project", build: { extensions: [ prismaExtension({ mode: "legacy", schema: "prisma/schema.prisma", migrate: true, typedSql: true, directUrlEnvVarName: "DATABASE_URL_UNPOOLED", }), ], },});
Use this mode when you're running Prisma 6.x or earlier with the standard prisma-client-js provider and no custom output directory.
Engine-Only Mode (Prisma 6.7+ with custom output)
For teams using Prisma 6.7+ with a custom output directory but still using the Rust-based engine. This mode gives you control over the client generation process, but will take care of installing the engine binaries for you when deploying.
prismaExtension({ mode: "engine-only", version: "6.19.0",});
Modern Mode (Prisma 7+)
The future is here. Prisma 7's new prisma-client removes Rust dependencies entirely, enabling faster installs and simpler deployments.
prismaExtension({ mode: "modern",});
Because of the simplicity of the Prisma 7 client, all this mode does is ensure the @prisma/client package is marked as an external dependency and not bundled during our build process, preventing potential issues with cross-module incompatibility.
Prisma generate
With both the new engine-only and modern modes, you will now be responsible for running the prisma generate step yourself. Only the legacy mode runs this step for you. This simplification brings us more in line with other deployment platforms and simplifies the extension, leading to fewer bugs and edge cases.
See our Prisma documentation for more information on how to run prisma generate when deploying to Trigger.dev.
Get started today
Update to Trigger.dev 4.1.1 to access the new Prisma extension:
npx trigger.dev@latest update
Then update your trigger.config.ts to specify the mode that matches your setup. Check out our Prisma documentation for detailed configuration examples and migration guides.