TRPC RSC calls forced to use no_store
Curious what the take is over here on having to flag every TRPC api call made server side with
I tried bringing this up over on the Next Discord since it feels more like an issue that Next should not be throwing an error. And having to use
Thoughts on this or recommended work arounds?
no_store, in order to avoid build errors from the next compiler?I tried bringing this up over on the Next Discord since it feels more like an issue that Next should not be throwing an error. And having to use
no_store in every RSC with a serevr side api call feels like a bit of an anti pattern. But they kind os suggested this was more of an issue with t3 or TRPC, which I an leaning towards disagreeing with.Thoughts on this or recommended work arounds?
