bug: prismaExtension's version detection only works when "@prisma/client" is added to additionalPackages #1480

Activity

1. Cirr0e commented on Nov 25, 2024

   

   Cirr0e

   on Nov 25, 2024

   More actions

   Hi! I understand the issue you're experiencing with the prismaExtension's version detection. This appears to be a known limitation in how the extension currently works with Prisma dependencies.

   Here's how to resolve this issue:

   1. Update your trigger.config.ts to use both the prismaExtension and additionalPackages together:

   import { defineConfig } from "@trigger.dev/sdk/v3";
   import { additionalPackages } from "@trigger.dev/build/extensions/core";
   import { prismaExtension } from "@trigger.dev/build/extensions/prisma";
   
   export default defineConfig({
     build: {
       extensions: [
         prismaExtension({ 
           schema: "prisma/schema.prisma"
           // Note: You don't need to specify version when using additionalPackages
         }),
         additionalPackages({ 
           packages: ["@prisma/client@5.22.0"] 
         }),
       ]
     }
   })

   This configuration ensures that:

   • The Prisma schema is properly loaded
   • The correct version of @prisma/client is available during build
   • The version detection will work correctly

   Be aware that:

   • You should match the version of @prisma/client to what's in your project's package.json
   • Make sure your DATABASE_URL environment variable is properly configured for deployment

   This is currently the recommended workaround until the version detection functionality is improved in a future release.

   Let me know if you need any clarification or run into any other issues!
2. RobertHH-IS commented on Dec 14, 2024

   

   RobertHH-IS

   on Dec 14, 2024

   More actions

   the build also fails if using prismaSchemaFolder extension.

   If schema.prisma
   `generator client {
   provider = "prisma-client-js"
   previewFeatures = ["postgresqlExtensions", "prismaSchemaFolder", "fullTextSearchPostgres"]
   }

   datasource db {
   provider = "postgresql"
   url = env("DATABASE_URL")
   }
   `

   And then you create other.prisma and user.prisma.. everything works fine in NextJS.. however trigger.dev build says that schema.prisma is empty and errors out.

   👍React with 👍1Reacted by HUORT Louis
3. rharkor commented on Feb 3, 2025

   

   rharkor

   on Feb 3, 2025

   Contributor

   More actions

   the build also fails if using prismaSchemaFolder extension.

   If schema.prisma `generator client { provider = "prisma-client-js" previewFeatures = ["postgresqlExtensions", "prismaSchemaFolder", "fullTextSearchPostgres"] }

   datasource db { provider = "postgresql" url = env("DATABASE_URL") } `

   And then you create other.prisma and user.prisma.. everything works fine in NextJS.. however trigger.dev build says that schema.prisma is empty and errors out.

   Yes, I'm currently having the same issue..
4. matt-aitken commented on Feb 3, 2025

   

   matt-aitken

   on Feb 3, 2025

   Member

   More actions

   @rharkor can you share your trigger.config file?

   We do support the folders, by following the convention that the enclosing folder should be called schema. You can see the code here:

   trigger.dev/packages/build/src/extensions/prisma.ts

   Line 115 in 6f52b00

   const usingSchemaFolder = dirname(this._resolvedSchemaPath).endsWith("schema");

   I know that people are using this, so maybe there's some new case here we don't deal with
5. rharkor commented on Feb 4, 2025

   

   rharkor

   on Feb 4, 2025

   Contributor

   More actions

   @rharkor can you share your trigger.config file?

   We do support the folders, by following the convention that the enclosing folder should be called schema. You can see the code here:

   trigger.dev/packages/build/src/extensions/prisma.ts

   Line 115 in 6f52b00
   const usingSchemaFolder = dirname(this._resolvedSchemaPath).endsWith("schema");

   I know that people are using this, so maybe there's some new case here we don't deal with

   Hey thanks for the reply, I've found the issue, it was because I am currently using multiple databases so I finally made my own small extension to handle that, if anyone have the same problem feel free to check the code below (please note that the paths aren't dynamic)

   import fs from "fs/promises"
   import path from "path"
   
   import { BuildExtension } from "@trigger.dev/build"
   
   export function prismaExtension(): BuildExtension {
     return {
       name: "prisma-extension",
       externalsForTarget(target) {
         if (target === "dev") {
           return []
         }
         return ["@prisma/client", "@prisma/engines"]
       },
       onBuildComplete: async (context, manifest) => {
         context.logger.debug("Copying the prisma schema to the output directory")
         //* Main database
         await fs.cp(
           path.join(__dirname, "../../../../../packages/database/main/prisma"),
           path.join(manifest.outputPath, "main-prisma", "prisma"),
           { recursive: true }
         )
         //* Logs database
         await fs.cp(
           path.join(__dirname, "../../../../../packages/database/logs/prisma"),
           path.join(manifest.outputPath, "logs-prisma", "prisma"),
           { recursive: true }
         )
   
         context.logger.debug(`Adding the prisma layer with the following commands`, {
           commands: ["cd main-prisma && npx prisma generate", "cd logs-prisma && npx prisma generate"],
           env: {},
           dependencies: {
             prisma: "latest",
           },
         })
         context.addLayer({
           id: "prisma",
           commands: ["cd main-prisma && npx prisma generate", "cd logs-prisma && npx prisma generate"],
           dependencies: {
             prisma: "latest",
           },
           build: {
             env: {},
           },
         })
       },
     }
   }
6. matt-aitken commented on Feb 4, 2025

   

   matt-aitken

   on Feb 4, 2025

   Member

   More actions

   @rharkor nice!
7. matt-aitken commented on Aug 29, 2026

   

   matt-aitken

   on Aug 29, 2026

   Member

   More actions

   The Prisma extension has been rewritten. It now detects the Prisma version without additionalPackages. Closing as outdated.
8. matt-aitken

   closed this as not plannedon Aug 29, 2026