Does deploying a new version of a tanstack start application break server actions?
An unfortunate thing that I have experienced with server actions in Next.js is that when the user is browsing the website on the current version, then I push a new version to production, the server actions no longer work and I get errors in return. Using API routes in Next.js solves this problem, but I'm liking the DX of server actions.
Is this also a problem in TanStack Start, where server actions only work on the currently deployed version, and then they break when a new version is deployed while the user is browsing?
2 Replies
rival-black•10mo ago
Yeah, I think the aim is to have support for skew protection down the line
xenial-black•10mo ago
My plan is to support at the very least a very crude form of skew protection by sending back a build header with every response. If it doesn’t match, we’ll force a refresh
Probably make this configurable too so you could instead show a notification to users to refresh
But none of that is there yet