URGENT: I cannot remove/uninstall Accelerate from my Vercel build. Help.
I'm trying to remove Accelerate, but Vercel's not having it. I've removed use of extend, removed the package library, changed environment URLs to original Postgres urls. I'm stumped. Please help.
9 Replies
In Vercel, I've purged the data cache. I'm not using the build cache. I've clear my browser cache. URL's have no use of prisma:// scheme. Could it be lurking in yarn.lock? I've removed use of
.$extends(withAccelerate()). I've removed @prisma/extension-accelerate from my project.I get this runtime error on Vercel:
prisma:error
Invalid
prisma.session.findUnique() invocation:
Error validating datasource db: the URL must start with the protocol prisma://
[next-auth][error][adapter_error_getSessionAndUser]
https://next-auth.js.org/errors#adapter_error_getsessionanduser
Invalid prisma.session.findUnique() invocation:
Error validating datasource db: the URL must start with the protocol prisma:// {
message: '\n' +
'Invalid prisma.session.findUnique() invocation:\n' +
'\n' +
'\n' +
'Error validating datasource db: the URL must start with the protocol prisma://',
stack: 'PrismaClientKnownRequestError: \n' +
'Invalid prisma.session.findUnique() invocation:\n' +
'\n' +
'\n' +
'Error validating datasource db: the URL must start with the protocol prisma://\n' +
' at In.handleRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6877)\n' +
' at In.handleAndLogRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6211)\n' +
' at In.request (/var/task/node_modules/.prisma/client/runtime/library.js:122:5919)\n' +
' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +
' at async l (/var/task/node_modules/.prisma/client/runtime/library.js:127:11167)\n' +
' at async getSessionAndUser (file:///var/task/node_modules/@auth/prisma-adapter/index.js:24:36)',
name: 'PrismaClientKnownRequestError'
}Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
continued...
[next-auth][error][SESSION_ERROR]
https://next-auth.js.org/errors#session_error
Invalid
prisma.session.findUnique() invocation:
Error validating datasource db: the URL must start with the protocol prisma:// PrismaClientKnownRequestError:
Invalid prisma.session.findUnique() invocation:
Error validating datasource db: the URL must start with the protocol prisma://
at In.handleRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6877)
at In.handleAndLogRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6211)
at In.request (/var/task/node_modules/.prisma/client/runtime/library.js:122:5919)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/var/task/node_modules/.prisma/client/runtime/library.js:127:11167)
at async getSessionAndUser (file:///var/task/node_modules/@auth/prisma-adapter/index.js:24:36) {
name: 'GetSessionAndUserError',
code: 'P6001'
}Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
Are you using the
accelerate or no-engine flags when creating Prisma Client?noengine
Using
npx prisma generate --no-engine on postinstall... (forgot), should I revert also to npx prisma generate?Correct
🙏 Ok Thank you, will try right away 🙂
While I have you, is it possible to use accelerate and directurl in the same runtime for different use cases?
directUrl is only used for commands that require a direct URL, like applying migrations.
If you have a need for both direct access and accelerate access, I’d reach out to support and explain your use case. We generally don’t recommend it.
Oh thank you, after reverting
no-engine it's working.
I'll reach out to support.