WaspW
Wasp•2y ago
WWWillems

Broke wasp db studio after migrating from Wasp 0.11 to 0.13

Hi đŸ‘‹

Wasp db studio seems to break after migrating from Wasp 0.11 to 0.13. I've followed the guide as outlined in the documentation, so I've first upgraded to 0.12 and afterwards to 0.13.

However, when I now try to run wasp db studio I'm getting following error:

Any idea on how to resolve this?

[   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:289
[   Db  !]             triggerUncaughtException(err, true /* fromPromise */);
[   Db  !]             ^
[   Db  !] 
[   Db  !] [Error: ENOENT: no such file or directory, rename '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0' -> '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'] {
[   Db  !]   errno: -2,
[   Db  !]   code: 'ENOENT',
[   Db  !]   syscall: 'rename',
[   Db  !]   path: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0',
[   Db  !]   dest: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'
[   Db  !] }
[   Db  !] 
[   Db  !] Node.js v20.3.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.13.2-inplace-cli-lib:Wasp.Cli.Command.Db.Studio
Was this page helpful?