- Automatically handles copying Prisma files to the build directory
- Generates the Prisma client during the deploy process
- Optionally will migrate the database during the deploy process
- 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)
This does not have any effect when running the
dev
command, only when running the deploy
command.Migrations
If you want to also run migrations during the build process, you can pass in themigrate
option:
clientGenerator
If you have multiplegenerator
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.
TypedSQL
If you are using TypedSQL, you’ll need to enable it via thetypedSql
option:
The
prismaExtension
will inject the DATABASE_URL
environment variable into the build process. Learn more about setting environment variables for deploying in our Environment Variables guide.These environment variables are only used during the build process and are not embedded in the final container image.If you’re experiencing database connection issues during deployment, you may need to add ?connection_limit=1
to your DATABASE_URL
to limit the number of concurrent connections during the build process.Using with Supabase Supavisor
When using Prisma with Supabase’s Supavisor pooler, use a pooled URL for Prisma Client and a session/direct URL for schema operations to avoid prepared statement conflicts. As of Feb 28, 2025, port 6543 runs Transaction Mode only; use port 5432 for Session Mode.Use the pooled connection (port 6543, Transaction Mode) for regular Prisma Client queries. Use the
session/direct connection (port 5432, Session Mode) for migrations and other schema operations.