Unable to Deploy to CloudFlare Workers using wrangler with Prisma

[gregavola]

I'm using Prisma as defined here, and I am able to run npm run dev have it working locally to serve content.

Once I run npm run build:worker && wrangler deploy - everything builds, but I get this error:

09:21:28.097 | ✘ [ERROR] Could not resolve "#main-entry-point"
-- | --
09:21:28.098 |  
09:21:28.098 | .worker-next/.next/standalone/node_modules/.prisma/client/default.js:1:30:
09:21:28.098 | 1 │ module.exports = { ...require('#main-entry-point') }
09:21:28.098 | ╵                               ~~~~~~~~~~~~~~~~~~~
09:21:28.099 |  
09:21:28.099 | The module "./wasm.js" was not found on the file system:
09:21:28.099 |  
09:21:28.099 | .worker-next/.next/standalone/node_modules/.prisma/client/package.json:114:19:
09:21:28.100 | 114 │         "workerd": "./wasm.js",
09:21:28.100 | ╵                    ~~~~~~~~~~~
09:21:28.100 |  
09:21:28.100 | You can mark the path "#main-entry-point" as external to exclude it from the bundle, which will remove this error. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.



09:21:28.101 | ✘ [ERROR] Build failed with 1 error:
-- | --
09:21:28.101 |  
09:21:28.101 | .worker-next/.next/standalone/node_modules/.prisma/client/default.js:1:30: ERROR: Could not resolve "#main-entry-point"
09:21:28.101

client.ts

import { Pool, neonConfig } from "@neondatabase/serverless";
import { PrismaNeon } from "@prisma/adapter-neon";
import { PrismaClient } from "@prisma/client";
import dotenv from "dotenv";
import ws from "ws";
dotenv.config();
neonConfig.webSocketConstructor = ws;
const connectionString = `${process.env.DATABASE_URL}`;
const pool = new Pool({ connectionString });
const adapter = new PrismaNeon(pool);
const prisma = new PrismaClient({ adapter });
export default prisma;

package.json

"dependencies": {
    "@aws-sdk/client-sqs": "^3.549.0",
    "@aws-sdk/util-utf8-node": "^3.259.0",
    "@neondatabase/serverless": "^0.9.5",
    "@prisma/adapter-neon": "^5.20.0",
    "@prisma/client": "^5.20.0",
    "@opennextjs/cloudflare": "^0.0.3",
    "dayjs": "^1.11.13",
    "dotenv": "^16.4.5",
    "next": "14.2.14",
    "pg": "^8.10.0",
    "prisma": "^5.20.0",
    "react": "^18",
    "react-dom": "^18",
    "ws": "^8.18.0",
    "zod": "^3.23.8"
  },
  "devDependencies": {
    "@types/node": "^20.16.10",
    "@types/pg": "^8.11.10",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "@types/ws": "^8.5.12",
    "bufferutil": "^4.0.8",
    "eslint": "^8",
    "eslint-config-next": "14.2.14",
    "ts-node": "^10.9.2",
    "typescript": "^5.6.2",
    "wrangler": "3.80.0"
  }

[vicb]

Hey @gregavola

• Do you have a GH repository with a repro
• Any chance that you asked the question on cloudflare Discord

Thanks

[gregavola]

I did, but I ended up re-writing this with drizzle, and it actually deployed. It just seems like Prisma was the issue.

[vicb]

Thanks for reporting.

Let's keep with open. I think Prisma is quite popuplar and we need to find a solution.

[vicb]

/ref opennextjs/opennextjs-cloudflare#71