bug: Prisma `prismaSchemaFolder` extension causes EISDIR error then fail deploy

[whchi]

Provide environment information

I encountered a similar error in #1565, attempted the proposed solution, but it did not work.
"@trigger.dev/sdk": "3.3.11"
"@prisma/client": "6.2.0"

Describe the bug

error message:

✘ [ERROR] Failed to apply extension PrismaExtension onBuildComplete SystemError [ERR_FS_EISDIR]: Path is a directory: cp returned EISDIR (/path/to/libs/prisma-schema/src/prisma/schema is a directory (not copied)) /path/to/libs/prisma-schema/src/prisma/schema

 {
    code: 'ERR_FS_EISDIR',
    info: {
      message:
  '/path/to/libs/prisma-schema/src/prisma/schema is a
  directory (not copied)',
      path: '/path/to/libs/prisma-schema/src/prisma/schema',
      syscall: 'cp',
      errno: 21,
      code: 'EISDIR'
    },
    errno: [Getter/Setter: 21],
    syscall: [Getter/Setter: 'cp'],
    path: [Getter/Setter:
  '/path/to/libs/prisma-schema/src/prisma/schema']
  }

Reproduction repo

not able to provide

To reproduce

the following configuration can reproduce same issue

• schema.prisma

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["strictUndefinedChecks", "prismaSchemaFolder", "relationJoins"]
  binaryTargets   = ["native", "debian-openssl-3.0.x"]
}

• package.json

...
  "prisma": {
    "schema": "./libs/prisma-schema/src/prisma/schema"
  }
...

• trigger.config.ts

defineConfig({
  build: {
    extensions: [
       additionalFiles({
          files: [
            './libs/prisma-schema/src/prisma/schema/nas.prisma',
            './libs/prisma-schema/src/prisma/schema/schema.prisma',
          ],
      }),
      additionalPackages({
        packages: ["@prisma/client@6.2.0"]
      }),
      prismaExtension({
        schema: './libs/prisma-schema/src/prisma/schema',
        version: '6.2.0',
        migrate: false,
      }),
})

Additional information

No response

[Hexatare]

I was able to fix the issue by just pointing to my schema.prisma file (the main file containing the generator and datasource), like this:

    build: {
        extensions: [
            prismaExtension({
                schema: "../../clients/database/prisma/schema/schema.prisma",
            }),
        ],
    },

But I do agree that the documentation is not very clear and this could be confusing.

[whchi]

I solved this issue by specifying each schema file, close it

    prismaExtension({
        schema: './libs/prisma-schema/src/prisma/schema/schema.prisma',
        version: '6.2.0',
        migrate: false,
      }),
      prismaExtension({
        schema: './libs/prisma-schema/src/prisma/schema/nas.prisma',
        version: '6.2.0',
        migrate: false,
      }),