Move prisma and prisma/client to peerDependencies and not direct dependencies?

[zackdotcomputer]

Currently the prisma and @prisma/client packages are listed as dependencies of this package. In practice, however, this package is always going to be used alongside those packages rather than expected to be in charge of managing those packages as dependencies. Therefore, I suggest we move those two to being peerDependencies instead of direct dependencies. This will avoid hard dependency conflicts or duplication if the user tries to use a version of prisma that's officially outside of the supported range of this package (whereas currently if we try to upgrade to prisma 6 while using this package, yarn installs both versions alongside each other instead of just giving a verbal warning about the mismatch).

[Brakebein]

Yes, it should be possible. I have recently upgraded from Prisma 4 to 5 and had to adapt some code, because the Prisma schema parser uses more strict types. But it should be backward compatible. Then, I will also need to test it for Prisma 6, and I will move any Prisma dependencies to peerDependencies section.