Compilation fails when importing "OrderByWithRelationInput" types about typegraphql-prisma

[MichalLytek]

It's on purpose. Because of #385, I don't have time to keep this lib always up to date.
And 90% of the time, Prisma version bumps don't break stuff. So I've changed ~ to ^ to let people try to use the newest version.

Maybe there should be a better warning or disclaimer that version x.y.z is tested and supported and newer might not work?

[SheaBelsky]

I understand that you lack the time/support to maintain this at the same level as before. As a result, I haven't upgraded to Prisma 4.16.2 since this library doesn't explicitly support it yet, exactly for the reason in this issue. If this library only explicitly supports version 4.15, then this library should reflect that so it's clear to implementors what the expectation is.

Maybe there should be a better warning or disclaimer that version x.y.z is tested and supported and newer might not work?

NPM would take care of this based on the version range OR on peer dependencies. If this library specifies peer dependencies for a specific version of Prisma, then NPM would warn developers if they try to use an incompatible version if Prisma. You could also add some sort of manual warning, but that seems like reinventing the wheel if NPM can already do something similar.

https://nodejs.org/fa/blog/npm/peer-dependencies

[MichalLytek]

then NPM would warn developers

No, now NPM yells and errors when you have wrong version. You have to force install the wrong package version.