How To Build a Prisma Client Extension

[@한별인]

Couldn't we inject the extends functionality into the prismaService in nestjs?

[@franky47]

2:29 what are the benefits of calling extends in the extension definition, compared to the object declaration syntax? Since the result of Prisma.defineExtension will be extended by users, wouldn't that be redundant?

[@PrismaData]

Thanks for your question! I'm sure others may have the same thoughts, so I'll explain. ***defineExtension*** is here for two purposes, but in simpler words, it's all about share-ability: - It allows you to define an extension outside of the client. You may want to keep it in a separate file. Also, you get the inference and the fancy types that you'd otherwise get on the $extends call. - If you're an extension author, it is the only way to define an extension so it can be shared as a package.

[@PrismaData]

What will you build with Prisma Client extensions? Remember to share them with us! Repo can be found here: github.com/sabinadams/prisma-field-picker

[@Broski_Rodragweez]

But you did still use map(), you just did so in side your extension rather then in the code that calls the prisma query.

[@Pesca.Shorts]

possible queryraw()?

[@justine_chang39]

awesome

[@t3ntube357]

why you wrote what you wrote???

[@jjoonjj714]

Is it possible to create an extension that uses the client with another extension?

[@PrismaData]

Yup! You can continue to extend a client to add more functionality.

[@jjoonjj714]

@@PrismaData Is there an example of this somewhere, would like to see it

[@PrismaData]

@@jjoonjj714 Hopefully this helps! www.prisma.io/docs/concepts/components/prisma-client/client-extensions#multiple-extensions