It seems the team is working on documenting the migration path. There’s an open issue discussing this: https://github.com/prisma/prisma/issues/3104 Please consider chiming in to make the conversation more public

So, is prisma-bindings being replaced by client completely (deprecated?) or is the understanding that both projects live side-by-side and exist for different use-cases. As I see right now prisma-client seems much less extensible than bindings without the ability to load relationships on objects. We might, then, assume that the client is to only be used in REST APIs, CLIs, and scripts? Otherwise, having to write relationship resolvers for every model seems to counter a large part of the product's value proposition.

I’m actually not sure yet, and have many of the same questions. In an answer from a maintainer further up this channel, he mentions that he recommends still using prisma-binding for relationships, but it seems like these changes are too new to say anything for certain

prisma-binding

is not going to be replaced by Prisma Client. They can be used together.

prisma-binding

is highly specialized on the use case of schema delegation. In other cases, using Prisma Client is recommended. Please keep an eye out on this discussion here, and add any higher level questions to the round. We will provide clarity here soon! https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394?u=nilan If you have more technical, specific questions, I would recommend opening a new Forum discussion all together 🙂

thanks @nilan