prisma: Prisma not working with sst monorepo

Bug description

SST is a framework to build serverless applications on aws and with the update to version 2.0 switched to a monorepo setup. Pre 2.0 it worked fine with prisma but since version 2.0 i ran into similar problems than other users have with nextjs.

They have an example setup with prisma where they have already a workaround applied to copy the prisma engines to the correct locations. This worked before v2.0 but now additional problems arise due to sst being a monorepo.

I already posted an issue on the sst git, but, as it is essentially a problem of prisma working with monorepos i decided to post it here aswell.

How to reproduce

• Create an sst project using: yarn create sst --template=examples/prisma
• run yarn install
• run yarn run dev // deploys lambdas structure to aws
• Response when running a lambda that accesses a prismaClient instance:

ReferenceError: __filename is not defined
|  +290ms      at Object.resolveEnginePath (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:99:280)
|  +291ms      at Object.getLibQueryEnginePath (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:73:1125)
|  +291ms      at Object.loadLibrary (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:73:561)
|  +291ms      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
|  +291ms      at Object.loadEngine (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:101:557)
|  +291ms      at Object.instantiateLibrary (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:100:1477)
|  +291ms      at Object.start (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:101:2081)
|  +291ms      at Object.getDmmf (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:101:3489)
|  +291ms      at <anonymous> (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:177:2864)
|  +291ms      at <anonymous> (/projects/test/prisma-test/node_modules/@prisma/client/runtime/library.js:177:3294) {
|  +291ms    clientVersion: '4.12.0'
|  +291ms  }

• response when running the project in a production environment (not SST’s lambda live dev) and accessing a function that accesses a prismaClient instance:

2023-03-29T15:10:57.786Z	undefined	ERROR	Uncaught Exception 	{
    "errorType": "Error",
    "errorMessage": "ENOENT: no such file or directory, open '/var/task/services/api/functions/schema.prisma'",
    "code": "ENOENT",
    "errno": -2,
    "syscall": "open",
    "path": "/var/task/services/api/functions/schema.prisma",
    "clientVersion": "4.12.0",
    "stack": [
        "Error: ENOENT: no such file or directory, open '/var/task/services/api/functions/schema.prisma'",
        "    at Object.openSync (node:fs:590:3)",
        "    at Object.readFileSync (node:fs:458:35)",
        "    at new LibraryEngine (file:///var/task/services/api/functions/index.mjs:29805:39)",
        "    at t3.getEngine (file:///var/task/services/api/functions/index.mjs:33428:20)",
        "    at new PrismaClient (file:///var/task/services/api/functions/index.mjs:33410:1118)",
        "    at file:///var/task/services/api/functions/index.mjs:58864:14",
        "    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)",
        "    at async Promise.all (index 0)",
        "    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)",
        "    at async _tryAwaitImport (file:///var/runtime/index.mjs:917:16)"
    ]
}

With prisma.schema copied to var/task/services/api/functions -> resolveEnginePath function of prisma accesses __filename which is not defined…

2023-03-29T15:29:12.684Z	fd320ee1-d78a-4e81-afe5-98f92c7e65ec	ERROR	ReferenceError: __filename is not defined
    at Object.resolveEnginePath (file:///var/task/services/api/functions/index.mjs:29737:58)
    at Object.getLibQueryEnginePath (file:///var/task/services/api/functions/index.mjs:29693:68)
    at Object.loadLibrary (file:///var/task/services/api/functions/index.mjs:29679:107)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.loadEngine (file:///var/task/services/api/functions/index.mjs:29865:58)
    at async Object.instantiateLibrary (file:///var/task/services/api/functions/index.mjs:29837:63)
    at async Object.start (file:///var/task/services/api/functions/index.mjs:29908:13)
    at async Object.getDmmf (file:///var/task/services/api/functions/index.mjs:29939:9)
    at async file:///var/task/services/api/functions/index.mjs:33385:24
    at async file:///var/task/services/api/functions/index.mjs:33391:186 {
  clientVersion: '4.12.0'
}

Environment & setup

• OS: Debian
• Database: MySql
• Node.js version: 18.15.0

Prisma Version

4.12.0