You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm considering moving from tRPC to Elysia for Nextjs/Vercel. I'm spoiled by end-to-end type safety so thats a requirement. Elysia seems cleaner with some advantages, but I've hit the wall.
In tRPC/Next I use unstable_cache on every project to cache heavy/large database queries, then revalidate them on db change. Really simple and cheap. However, as far as I understand now, unstable_cache (which use server components context) does not work on Elysia/API routes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm considering moving from tRPC to Elysia for Nextjs/Vercel. I'm spoiled by end-to-end type safety so thats a requirement. Elysia seems cleaner with some advantages, but I've hit the wall.
In tRPC/Next I use unstable_cache on every project to cache heavy/large database queries, then revalidate them on db change. Really simple and cheap. However, as far as I understand now, unstable_cache (which use server components context) does not work on Elysia/API routes.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions