Backwards compatible deployments with trpc?
Throwing this in a thread to see if anyone’s got some opinions on this topic. Due to the zod validation in the trpc handlers, your frontend and backend deployments must always be in sync in order to avoid runtime errors.
If you make a breaking change and somehow an outdated/stale bit of frontend code hits a newer deployment of the API, things will break.
I feel like this possibility is not often discussed or even encountered as we tend to use trpc with next js and vercel. So coincidentally the frontend and backend deployments stay in sync.
If you make a breaking change and somehow an outdated/stale bit of frontend code hits a newer deployment of the API, things will break.
I feel like this possibility is not often discussed or even encountered as we tend to use trpc with next js and vercel. So coincidentally the frontend and backend deployments stay in sync.
