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
Understand easily the caching and invalidating cache is working properly as planned and expected
Non-Goals
Wasting time, money, and effort of the Vercel team and all the Next.js users
Background
I believe the final touch that makes me feel as comfortable as using tRPC + RQ is its DevTool, because it helps me understand my caching strategy and invalidating strategy is working as planned.
My current approach is using RQ + Server Actions + RQ DevTools. I only need Server Actions and the DevTool of RQ. I don't need RQ. Except I'm working on another project which is a Monorepo, tRPC + RQ (sometimes with RSA) is still the Most Effective Tactic Available.
Proposal
cmd + c, cmd + v from RQ DevTool to Next.js codebase, then change the logo and adapt the integration. Voila! Mama Mia Lezatos!
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
-
Goals
Non-Goals
Background
I believe the final touch that makes me feel as comfortable as using tRPC + RQ is its DevTool, because it helps me understand my caching strategy and invalidating strategy is working as planned.
My current approach is using RQ + Server Actions + RQ DevTools. I only need Server Actions and the DevTool of RQ. I don't need RQ. Except I'm working on another project which is a Monorepo, tRPC + RQ (sometimes with RSA) is still the Most Effective Tactic Available.
Proposal
cmd + c, cmd + v from RQ DevTool to Next.js codebase, then change the logo and adapt the integration. Voila! Mama Mia Lezatos!
Beta Was this translation helpful? Give feedback.
All reactions