revalidate tag

[goughfey]

in case of data fetching in nextjs server component, how to revalidate an endpoint using tags provided in fetch options. Is there any way to add next: {tags: ['user']} orpc client ...?

[dosubot]

Hi @goughfey! I'm Dosu and I’m helping the orpc team.

The orpc client does not natively support passing Next.js fetch options like next: {tags: ['user']} for cache revalidation in server components. While orpc lets you customize fetch functions and headers, these options are not mapped to Next.js infrastructure features such as revalidation tags or cache control out of the box (docs, code).

If you need tag-based revalidation, you would need to implement a custom fetch adapter or patch the fetch logic in your SSR/server components to inject the next option manually. The current integration focuses on dynamic headers and context, not on Next.js cache tags (example).

Let me know if you want guidance on building a custom adapter or patching fetch for this use case.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[unnoq]

You can use client context: https://orpc.unnoq.com/docs/client/rpc-link#using-client-context