Old client after server update

What's the best way to handle an old client trying to request an asset or API that no longer exists after the server has been rebuilt and redeployed? The current behaviour of my SolidStart app is that the client crashes and in my <ErrorBoundary> I have a fallback that shows a link that takes them back to the web app by doing a full page reload (I make sure to have target="_self"). Ideally, I'd like to be able make the client automatically reload the page if it detects the server has been updated. If it could do this page reload during a navigation most user's would hardly notice it. Thanks.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?