[TRI-5172] Compatibility with Prisma 6.6+

[matt-aitken]

In Prisma 6.6.0+ they require an output path and no longer generate the Prisma client in node_modules.

Details here.

This is going to cause problems with our official prisma extension which was built to deal with the old way.

It seems like the way to fix this would be to do this from their docs:

pass the the --schema option to your Prisma CLI command (e.g. prisma migrate dev --schema ./prisma/schema)

We don't pass the --schema for folders right now I don't think

_TRI-5172

[mfts]

Correct, you explicitly don't add the --schema flag when schemaFolder was detected

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

Lines 186 to 190 in 0b2eb34

	commands.push(
	`${binaryForRuntime(
	manifest.runtime
	)} node_modules/prisma/build/index.js generate ${generatorFlags.join(" ")}` // Don't add the --schema flag or this will fail
	);

i think this should fix it:

for schema folder:

commands.push(
        `${binaryForRuntime(
          manifest.runtime
        )} node_modules/prisma/build/index.js generate --schema=./prisma/schema ${generatorFlags.join(" ")}` // Add the --schema flag for prisma@^6.6.0 compatibilty
      );

for schema file

commands.push(
        `${binaryForRuntime(
          manifest.runtime
        )} node_modules/prisma/build/index.js generate --schema=./prisma/schema.prisma ${generatorFlags.join(" ")}` // Add the --schema flag for prisma@^6.6.0 compatibilty
      );

[ericallam]

@mfts as a workaround for now, you can specify the path to the prisma schema in your package.json like this:

"prisma": {
    "schema": "prisma/schema"
  }

[mfts]

@ericallam ok cool. I'll try that.

[ericallam]

It looks like our extension is going to need some extensive updates to fully support Prisma 6.6.0:

• Handle prisma.config.ts file if it exists, and potentially use it's values to configure the extension
• The schema location is no longer automatically detected (see their docs on this here: https://www.prisma.io/docs/orm/prisma-schema/overview/location)
• We need to stop inferring if the schema dir is being used by looking at the parent dir of the schema.prisma file and assuming it will be named schema

[ericallam]

For anyone running into issues with 6.6.0, when using prismaSchemaFolder feature

• Make sure your schema.prisma file is located inside prisma/schema, alongside your other .schema files.
• Move your migrations dir into the same dir as the schema.prisma file
• Make sure you specify the schema option in the prismaExtension call to point at the schema.prisma file
• Specify the "schema" path that prisma generate will use in your package.json where your trigger.config.ts lives to point to prisma/schema (see my comment above)

[manuelbiermann]

I did not manage to get his to work on my end. I did figure out another workaround though. It seems to work to use the new setup within your app and generate an old client specifically for trigger:

schema.prisma

generator client {
  provider = "prisma-client"
  output   = "../app/generated/prisma"
}

generator triggerDevClient {
  provider = "prisma-client-js"
}

trigger.config.ts

build: {
    extensions: [
      prismaExtension({
        schema: "prisma/schema.prisma",
        version: "6.6.0",
        clientGenerator: "triggerDevClient",
      }),
    ],
  },