NextJS Prisma Deconfliction
Unanswered
Kokoni posted this in #help-forum
KokoniOP
NextJS does
Basically, I want to be able to perform 3 identical Prisma queries and only have it act as 1 on the SSR.
If all three of these components, Next should have some sort of driver to deconflict these. The optimal API in my mind would be a custom interceptor that interfaces between the Next caching code and the third party package. Of course, the third party package would have to have a place to intercept in the first place...
Is there a way right now to do this sort of deconfliction outside of a custom unstable cache implementation?
fetch deconfliction. I think that it would be really interesting if this API could be genericized into deconflicting most third-party things. I know unstable-cache attempts to accomplish some of this, but it's not exactly the same.Basically, I want to be able to perform 3 identical Prisma queries and only have it act as 1 on the SSR.
A (getUser)
|-> B (getUser)
|-> C (getUser)If all three of these components, Next should have some sort of driver to deconflict these. The optimal API in my mind would be a custom interceptor that interfaces between the Next caching code and the third party package. Of course, the third party package would have to have a place to intercept in the first place...
Is there a way right now to do this sort of deconfliction outside of a custom unstable cache implementation?