I have very often this when I run wasp db studio :
[ Db ] Environment variables loaded from .env [ Db ] Prisma schema loaded from ../db/schema.prisma [ Db ] Prisma Studio is up on http://localhost:5555 [ Db !] node:internal/process/promises:288 [ Db !] triggerUncaughtException(err, true /* fromPromise */); [ Db !] ^ [ Db !] [ Db !] [Error: ENOENT: no such file or directory, rename '/Users/estellejacot/Library/Caches/checkpoint-nodejs/.81644.0' -> '/Users/estellejacot/Library/Caches/checkpoint-nodejs/prisma-studio-default'] { [ Db !] errno: -2, [ Db !] code: 'ENOENT', [ Db !] syscall: 'rename', [ Db !] path: '/Users/estellejacot/Library/Caches/checkpoint-nodejs/.81644.0', [ Db !] dest: '/Users/estellejacot/Library/Caches/checkpoint-nodejs/prisma-studio-default' [ Db !] } [ Db !] [ Db !] Node.js v18.18.0 Internal Wasp error (bug in compiler): This should never happen, studio should never stop. CallStack (from HasCallStack): error, called at cli/src/Wasp/Cli/Command/Db/Studio.hs:29:3 in waspc-0.12.1-inplace-cli-lib:Wasp.Cli.Command.Db.Studio
Most of the time, I re-run exactly the same few times and it works again, but if you could fix it it would be nice!
Thanks
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.