prisma.$use() deprecated

[ikbenignace]

Since 4.16.0, released today, prisma.$use() is deprecated so we should change the way we add the middleware.

[franky47]

Thanks for the heads-up, looks like query extension components are the way to go.

If anyone wishes to try their hand at a PR, I'll be happy to give them a hand.

[ikbenignace]

I'm trying to figure it out, but it looks way different

[ikbenignace]

I think I will stick to 4.15.0 for a while

[franky47]

From what I read in the release notes, middlewares with $use are deprecated but still supported for a handful of versions, so it should work fine with 4.16.0 onwards.

That being said, migrating to the extensions mechanism will be required at some point.

[ikbenignace]

I do not know if it has something to do with the $use on 4.16, but I can not do a where call anymore on email, even though I have a emailHash.

Do you have a discord server for discussions?

[franky47]

That's odd, the integration test suite passes fine with 4.16.0.

Do you have a discord server for discussions?

I don't. I prefer discussions to remain public, localised, and searchable by others that may encounter the same problem.

[ikbenignace]

I understand. I think the middleware works for me, atleast I get the data as decrypted data, but the where function doens't really work anymore, don't know yet what I've changed, but this is off topic.

[franky47]

If you get to the bottom of it and find something odd that isn't covered by the test suite, please let me know.

[ikbenignace]

Your test case seems fine, I'm just wondering whats wrong with my implementation since every emailHash is different altough it is the same email address

[franky47]

That sounds like a double application of the middleware, are you using Next.js by any chance? We've had issues with hot module reloading in the past, see #61.

[ikbenignace]

I'm using Nestjs and I found the issue because #61, you only should use the middleware once. I did this in every service, but since we use dependency injection, it was applied multiple times, which doubles every process. You only have to add the middleware on your PrismaService

[ikbenignace]

Okay forgot this above statement, the data is now unencrypted :p

[ikbenignace]

I don't really know how to use it, because I want to use it on initialization, but for some reason, it will not encrypt anything in the services of each controller, don't know how else or where I should use the middleware

[franky47]

Usually with other backend frameworks (Next.js, Fastify, Express), I create the Prisma client in a dedicated file where I connect the middlewares before exporting the configured client. Then route handlers / controllers can import the client from there (or use whatever dependency injection mechanism is built into the framework) to perform queries.

See https://github.com/47ng/prisma-field-encryption/blob/next/src/tests/prismaClient.ts