Bug description
We've decided to try out the multi-schema setup and apparently the Prisma extension stopped working as soon as we changed the shcema property in prisma config to prisma/ folder. Also, veeery weird errors were showing in the extension's output:
[Error: EPERM: operation not permitted, scandir '/Users/work/.Trash'] {
errno: -1,
code: 'EPERM',
syscall: 'scandir',
path: '/Users/work/.Trash'
}
In fact, it contained a lot of logs for scandir errors for completely random path locations for random macos system user directories, and the paths included Documents, .Trash, Downloads: really weird and suspicious!
How to reproduce
Our config:
export default defineConfig({
schema: "prisma/",
migrations: {
path: "prisma/migrations",
seed: "tsx prisma/seed.ts",
},
datasource: {
// Use placeholder during build (e.g. pnpm generate); real URL at runtime for migrate/seeds
url:
process.env.DATABASE_URL ??
"postgresql://placeholder:placeholder@localhost:5432/placeholder",
},
});
prisma generate works, just the extension crashes. As for the rest – we have only 1 schema file: schema.prisma:
datasource db {
provider = "postgresql"
}
generator client {
provider = "prisma-client"
output = "../src/core/prisma/generated"
moduleFormat = "cjs" // Matches Prisma's output format with NestJS's CommonJS runtime environment.
previewFeatures = ["relationJoins"]
}
generator typegraphql {
// provider = "typegraphql-prisma-select-nestjs"
// provider = "node /Users/mac/auditorium/typegraphql-prisma-nestjs-select/src/cli/dev.ts"
provider = "node ./prisma/generator/src/cli/dev.ts"
output = "../src/core/graphql/#generated"
useSimpleInputs = true
}
// ==================== Enums ====================
enum Role {
...
Prisma information
Prisma v. 7.9.0
Additional logs from the extension's output:
Node.js v24.15.0
[Info - 7:52:14 PM] Connection to server got closed. Server will restart.
[Info - 7:52:14 PM] Default version of Prisma 'prisma-schema-wasm': 3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:14 PM] Extension name @prisma/language-server with version 31.11.0
[Info - 7:52:14 PM] Prisma Engines version: 7.8.0-6.3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:14 PM] Prisma CLI version: 7.9.0-dev.4
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: EPERM: operation not permitted, scandir '/Users/work/.Trash'] {
errno: -1,
code: 'EPERM',
syscall: 'scandir',
path: '/Users/work/.Trash'
}
Node.js v24.15.0
[Info - 7:52:19 PM] Connection to server got closed. Server will restart.
[Info - 7:52:19 PM] Default version of Prisma 'prisma-schema-wasm': 3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:19 PM] Extension name @prisma/language-server with version 31.11.0
[Info - 7:52:19 PM] Prisma Engines version: 7.8.0-6.3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:19 PM] Prisma CLI version: 7.9.0-dev.4
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: EACCES: permission denied, scandir '/Users/Test/Library'] {
errno: -13,
code: 'EACCES',
syscall: 'scandir',
path: '/Users/Test/Library'
}
Node.js v24.15.0
[Info - 7:52:24 PM] Connection to server got closed. Server will restart.
[Info - 7:52:24 PM] Default version of Prisma 'prisma-schema-wasm': 3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:24 PM] Extension name @prisma/language-server with version 31.11.0
[Info - 7:52:24 PM] Prisma Engines version: 7.8.0-6.3c6e192761c0362d496ed980de936e2f3cebcd3a
[Info - 7:52:24 PM] Prisma CLI version: 7.9.0-dev.4
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: EACCES: permission denied, scandir '/Users/Test/Downloads'] {
errno: -13,
code: 'EACCES',
syscall: 'scandir',
path: '/Users/Test/Downloads'
}
Node.js v24.15.0
[Error - 7:52:29 PM] Connection to server got closed. Server will not be restarted.
Environment & setup
- OS: macOS 15.5 (24F74)
- Editor: VSCode (or Cursor)
- Editor version: 1.118.1
- Extension version: 31.11.0
Bug description
We've decided to try out the multi-schema setup and apparently the Prisma extension stopped working as soon as we changed the
shcemaproperty in prisma config toprisma/folder. Also, veeery weird errors were showing in the extension's output:In fact, it contained a lot of logs for
scandirerrors for completely random path locations for random macos system user directories, and the paths includedDocuments,.Trash,Downloads: really weird and suspicious!How to reproduce
Our config:
prisma generateworks, just the extension crashes. As for the rest – we have only 1 schema file:schema.prisma:Prisma information
Prisma v. 7.9.0
Additional logs from the extension's output:
Environment & setup