Support Prisma 5.0.0 version

[Abdulrahman Elheyb]

I have updated my npm packages to the new version when I did this I got an error while installing the packages

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: project-api@0.0.1
npm ERR! Found: @prisma/client@5.0.0
npm ERR! node_modules/@prisma/client
npm ERR!   @prisma/client@"^5.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @prisma/client@"^4" from @paljs/plugins@5.3.3
npm ERR! node_modules/@paljs/plugins
npm ERR!   @paljs/plugins@"^5.3.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[belmeopmenieuwesim]

@AhmedElywa Can we just add ^5.0 support here: "@prisma/client": "^4.15.0",

[Ahmed Elywa]

There are a lot of breaking changes that need to handle first before releasing the new version supporting Prisma. V5

[Ahmed Elywa]

we pushed V6 that support prisma v5

[Andrew Porritt]

Trying to install the latest version gives an error:

npm ERR! Found: @prisma/client@5.2.0
npm ERR! node_modules/@prisma/client
npm ERR!   @prisma/client@"^5.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @prisma/client@"^4" from @paljs/plugins@6.0.1
npm ERR! node_modules/@paljs/plugins
npm ERR!   @paljs/plugins@"^6.0.0" from the root project

It looks like the packages still have a dependency on Prisma 4

[Ahmed Elywa]

Oh yes, I forgot to change the peer dependency will fix it.

[Ahmed Elywa]

Fixed in v6.0.2