v3.7.0 and above immediately crashes Next.js app
See original GitHub issueBug description
I’ve been using Prisma and Next.js together for quite a while.
When I upgrade Prisma to 3.7.0 or above, and then run my Next.js app, it immediately crashes the process when I load any page.
The console just gives:
zsh: killed npm run dev
Is there any more useful logging I could get, to help debug this? Has anything changed in 3.7.0 which could cause this? I have tested with 3.8.0 too and it gives the same result. I’m using the latest version of Next.js 12.0.8 Thanks
How to reproduce
Expected behavior
No response
Prisma information
Environment & setup
- OS: Mac OS
- Database: MySQL RDS
- Node.js version: 16.13.0
Prisma Version
3.7.0 and above
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (7 by maintainers)
Top Results From Across the Web
Looking for possible reasons why Next.js Node Server crashes
Failed at the nextjs@0.1.0 dev script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above....
Read more >Why this nextjs code is crashing ? - YouTube
Link to my programming Video Library:https://courses.LearnCodeOnline.in/learnPick best UI color for your projects:https://UIColorPicker.
Read more >NextJS Crash Course in 2Hrs - Learn NextJS With one Project
Premium React Course: https://zinotrustacademy.com/reactAll courses: https://zinotrustacademy.com/coursesFREE React ...
Read more >In iOS 15, when the app is restarted, it immediately crashes.
After the iOS 15 update, the following process causes the app to die. Go to the home screen while running the app; Completely...
Read more >How to troubleshoot kernel crashes, hangs, or reboots with ...
At the moment of a kernel panic the secondary kernel will boot up, collect, compress and dump the first kernel's memory based on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FWIW I ran into this exact same problem. Running
rm -rf node_modules; npm i
fixed it for me, so likely something strange being cached.I also had this issue (not in Next) right now on macOS. Removing the
./node_modules/.prisma
folder and runningprisma generate
again solved this issue.I hope it helps somebody.