ReferenceError: prisma is not defined :( | Trigger.dev | Page 1

ocean sapphire Apr 2, 2024, 6:46 AM

#

Everything working fine locally, but production is failing with ReferenceError: prisma is not defined (I use prisma in the job tasks themselves)

Stack trace, in case it matters:

ReferenceError: prisma is not defined
    at cx (/var/task/.next/server/app/api/trigger/route.js:2:210384)
    at cF (/var/task/.next/server/app/api/trigger/route.js:6:5445)
    at t.runTask.name (/var/task/.next/server/app/api/trigger/route.js:6:62545)
    at executeTask (/var/task/.next/server/app/api/trigger/route.js:2:159977)
    at AsyncLocalStorage.run (node:async_hooks:338:14)
    at oB.runTask (/var/task/.next/server/app/api/trigger/route.js:2:161788)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.run (/var/task/.next/server/app/api/trigger/route.js:6:62474)
    at async #executeJob (/var/task/.next/server/app/api/trigger/route.js:2:195875)
    at async cu.handleRequest (/var/task/.next/server/app/api/trigger/route.js:2:185917)

raven brook Apr 2, 2024, 12:20 PM

#

This is strange as with v2 your code is running wherever you normally deploy. Are you using Prisma in your Next.js app, other than in your Trigger jobs?

naive totem Apr 2, 2024, 6:42 PM

#

^ This reads to me like you might have prisma as a dev-dependency so it works locally but doesn't play nice when deployed in production

raven brook Apr 2, 2024, 9:55 PM

#

@ocean sapphire the official Prisma guidance is to use the postinstall script to generate the client. https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel

Prisma

Deploy to Vercel

Learn how to deploy a Next.js application based on Prisma Client to Vercel.

#ReferenceError: prisma is not defined :(