Module not found after v6.5.0 upgrade
After upgrading to v6.5.0 these errors occur.
3 Replies
You selected the bot's instantaneous insights. Let me compile your answer right away!
The error you're encountering is related to using Prisma in a Next.js environment, specifically in an Edge Runtime context. The errors indicate that your application is trying to use Node.js built-in modules (
os and crypto) which aren't available in the Edge Runtime.
Why this happens
This is a common issue when using Prisma in serverless or edge environments. The error occurs because:
1. Prisma Client is trying to use Node.js built-in modules (os and crypto)
2. Next.js Edge Runtime doesn't support these Node.js modules
3. This is particularly problematic when using Prisma with auth adapters in edge functions
Solutions
There are a few approaches to solve this issue:
1. Move authentication logic to Node.js runtime
The simplest solution is to ensure your auth routes are not using the Edge Runtime. In Next.js, you can do this by:
- Making sure your auth API routes don't use the export const runtime = 'edge' directive
- Moving your auth logic to regular Node.js API routes instead of Edge functions
2. Use experimental-serverless-trace target (for older Next.js versions)
For older Next.js versions, adding this to your next.config.js might help:
This solution was reported to work in this GitHub issue.
3. Use a custom output path for Prisma Client
If you're using pnpm (as indicated by your error paths), you might need to specify a custom output path for your Prisma Client. In your schema.prisma:
Then import from this custom path instead of @prisma/client.
4. Downgrade Prisma
As a temporary workaround, you could downgrade to a previous version that worked for you until a fix is available.
Additional context
This issue appears to be related to how Prisma Client h
andles Node.js built-in modules in environments that don't support them. Similar issues have been reported in various GitHub issues when using Prisma in edge environments.
For Next.js 15 specifically, there are ongoing discussions about compatibility with Prisma in edge functions, as mentioned in this GitHub issue.
I hope one of these solutions helps resolve your issue!
🤔 Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly.
In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.I did not have this problem on v6.4.0
Hey 👋
Can you please provide a minimal reproduction so that I can test?