Hey so we were waiting to consider going to prisma2 based on how all of the new nexus plugin stuff, which is now called

nexus-prisma

for prisma2 was going to shake out. I know it’s in early preview right now, but I noticed you guys just archived the graphql-nexus channel, which makes me believe that path might be getting abandoned. Can I get any more future clarification on whether there is still any sort of commitment to having that whole story supported moving forward with prisma2. I know it’s not a main focus, but I need to know if it’s going to ultimately going to be semi-abandoned or not because it doesn’t align very much at all anymore with where prisma is heading, and so I should plan my migration path to be without the ability to continue to have auto-generated CRUD based on my schema or not. I know that there are other threads historically that have attempted to address this, but they’re pretty old now and I am curious if anyone else is in the same boat as us in this community channel, or if @nikolasburk would be willing to point me to another more recent discussion about this topic in a github thread somewhere or mention some thoughts here.

Hey there Tyler 👋 thanks for reaching out!

I noticed you guys just archived the graphql-nexus channel,

We’ve archived this channel in an effort to restructure our Slack and have a clearer channel structure. We are also indeed not “official maintainers” of the GraphQL Nexus library and from that perspective, the channel doesn’t really “belong” into the official Prisma Slack (since we don’t have channels for alternatives like TypeGraphQL or Pothos either).

we were waiting to consider going to prisma2 based on how all of the new nexus plugin stuff, which is now called

nexus-prisma

for prisma2 was going to shake out.

Can I get any more future clarification on whether there is still any sort of commitment to having that whole story supported moving forward with prisma2. I know it’s not a main focus, but I need to know if it’s going to ultimately going to be semi-abandoned or not because it doesn’t align very much at all anymore with where prisma is heading, and so I should plan my migration path to be without the ability to continue to have auto-generated CRUD based on my schema or not.

This is a really valid question and we’ve been working internally to clarify the situation here over the past couple of months! The TLDR is: • We’re handing over nexus-prisma to our community member (an announcement on GitHub about this will follow soon). • It doesn’t seem like nexus-prisma will support auto-generated CRUD operations in the near- or mid-term future. • If you need auto-generated CRUD operations for your app, the current alternatives are: ◦ https://prisma.typegraphql.com/ (see this tutorial) ◦ https://paljs.com/generator/ (I just saw that this might actually also work with Nexus, maybe @Ahmed can give more info about this since he’s the author of Pal.js) How to get generated CRUD resolvers for Prisma models