/entry.js:1:21: Could not resolve: "node:fs". Maybe you need to "bun install"? at /home/runner/work/bun/bun/test/bundler/expectBundled.ts:738:16 at /home/runner/work/bun/bun/test/bundler/expectBundled.ts:408:10

/entry.js:2:25: Could not resolve: "node:buffer". Maybe you need to "bun install"? /entry.js:3:32: Could not resolve: "node:child_process". Maybe you need to "bun install"? /entry.js:4:26: Could not resolve: "node:cluster". Maybe you need to "bun install"? /entry.js:5:27: Could not resolve: "node:console". Maybe you need to "bun install"? /entry.js:6:28: Could not resolve: "node:constants". Maybe you need to "bun install"? /entry.js:7:25: Could not resolve: "node:crypto". Maybe you need to "bun install"? /entry.js:8:24: Could not resolve: "node:dgram". Maybe you need to "bun install"? /entry.js:9:22: Could not resolve: "node:dns". Maybe you need to "bun install"? /entry.js:10:25: Could not resolve: "node:domain". Maybe you need to "bun install"? /entry.js:11:25: Could not resolve: "node:events". Maybe you need to "bun install"? /entry.js:12:21: Could not resolve: "node:fs". Maybe you need to "bun install"? /entry.js:13:23: Could not resolve: "node:http". Maybe you need to "bun install"? /entry.js:14:24: Could not resolve: "node:https". Maybe you need to "bun install"? /entry.js:15:26: Could not resolve: "node:module". Maybe you need to "bun install"? /entry.js:16:22: Could not resolve: "node:net". Maybe you need to "bun install"? /entry.js:17:21: Could not resolve: "node:os". Maybe you need to "bun install"? /entry.js:18:23: Could not resolve: "node:path". Maybe you need to "bun install"? /entry.js:19:29: Could not resolve: "node:perf_hooks". Maybe you need to "bun install"? /entry.js:20:26: Could not resolve: "node:process". Maybe you need to "bun install"? /entry.js:21:27: Could not resolve: "node:punycode". Maybe you need to "bun install"? /entry.js:22:30: Could not resolve: "node:querystring". Maybe you need to "bun install"? /entry.js:23:27: Could not resolve: "node:readline". Maybe you need to "bun install"? /entry.js:24:23: Could not resolve: "node:repl". Maybe you need to "bun install"? /entry.js:25:25: Could not resolve: "node:stream". Maybe you need to "bun install"? /entry.js:26:33: Could not resolve: "node:string_decoder". Maybe you need to "bun install"? /entry.js:27:22: Could not resolve: "node:sys". Maybe you need to "bun install"? /entry.js:28:25: Could not resolve: "node:timers". Maybe you need to "bun install"? /entry.js:29:22: Could not resolve: "node:tls". Maybe you need to "bun install"? /entry.js:30:22: Could not resolve: "node:tty". Maybe you need to "bun install"? /entry.js:31:22: Could not resolve: "node:url". Maybe you need to "bun install"? /entry.js:32:23: Could not resolve: "node:util". Maybe you need to "bun install"? /entry.js:33:21: Could not resolve: "node:v8". Maybe you need to "bun install"? /entry.js:34:21: Could not resolve: "node:vm". Maybe you need to "bun install"? /entry.js:35:23: Could not resolve: "node:zlib". Maybe you need to "bun install"? at /home/runner/work/bun/bun/test/bundler/expectBundled.ts:738:16 at /home/runner/work/bun/bun/test/bundler/expectBundled.ts:408:10

Received: undefined at /home/runner/work/bun/bun/test/js/node/fs/fs.test.ts:1476:2

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:50:16 47 test( 48 "CRUD basics", 49 async (prisma: PrismaClient, testId: number) => { 50 const user = await prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7301

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:92:16 89 test( 90 "CRUD with relations", 91 async (prisma: PrismaClient, testId: number) => { 92 const user = await prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7301

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:139:20 136 async (prisma: PrismaClient, testId: number) => { 137 const users = await Promise.all( 138 new Array(10).fill(0).map((_, i) => 139 prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/sqlite/client/runtime/library.js:122:7301

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:50:16 47 test( 48 "CRUD basics", 49 async (prisma: PrismaClient, testId: number) => { 50 const user = await prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7301

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:92:16 89 test( 90 "CRUD with relations", 91 async (prisma: PrismaClient, testId: number) => { 92 const user = await prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7301

/home/runner/work/bun/bun/test/js/third_party/prisma/prisma.test.ts:139:20 136 async (prisma: PrismaClient, testId: number) => { 137 const users = await Promise.all( 138 new Array(10).fill(0).map((_, i) => 139 prisma.user.create( Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-3.0.x"] } The following locations have been searched: /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/.prisma/client /tmp/prisma-engines /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres at new _ (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:26:1709) at handleRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:8580) at handleAndLogRequestError (/home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7691) at /home/runner/work/bun/bun/test/js/third_party/prisma/prisma/postgres/client/runtime/library.js:122:7301

4 files with failing tests