Upgrade to Prisma 2 Beta 3

[ianwensink]

Description

The nexus-plugin-prisma module at 0.7.0 has a direct dependency on the @prisma modules, fixed at beta1. At the time of writing we are already at beta3, which means people using Nexus are missing out on all of that.

When you require beta3 of either the cli or the client, NPM will install both versions, causing issues when generating the Prisma client. Nexus will do it in the local (beta1) folder, while the rest of your app is using the shared node_modules (beta3).

Imho, solving this could be through either upgrading to the latest beta, but more future proof would be to have the prisma modules as peer dependencies, with the risk of upgrading for the user.

Repro

1. npm install @prisma/cli@2.0.0-beta.3
2. This will result in node_modules/@prisma/cli (at beta3) and node_modules/nexus-plugin-prisma/node_modules/@prisma/cli (at beta1)

[jasonkuhrt]

but more future proof would be to have the prisma modules as peer dependencies

Feel free to open an issue to discuss that idea. Nexus Prisma plugin is currently working as intended however. Either users are going open feature requests to ask for upgrades or they are going to open bug reports when the BYOP (bring your own prisma) integration fails.

It is on us (Labs team) to stay on top of the Prisma 2 releases but the benefit of being able to bring up a graphql api with prisma with only two deps that are more or less guaranteed to work together with zero headache is something we're not ready to let go of yet.

We do need to write docs about our strategy on this though! graphql-nexus/nexus#767

[ianwensink]

@jasonkuhrt, I totally get what you're saying :). My comment about being future proof was obviously without any knowledge about your internal processes, so if upgrading every time works for you, keep up the good work!

Thanks for your swift support and creation of a pull request. Hopefully we can release it soon and enjoy 0.8.0 as well (need the passing of Prisma client options ;-).

Thanks!