-
|
Is x-script content-type is stable? What I mean by that. Is that is it backward-compatible between versions if the API of the action/loader stays backward-compatible? I just want to know how resilient react-router is in framework mode to version skew when making blue-green deployments. E.g. so older clients will be working fine with newer servers, despite being a bit behind. For example, Next.js server actions and RSC are not, and it's hell on earth to handle infra-wise (possible, but unnecessary complication) so you have guaranteed downtime every time you deploy, and the client breaks even from non-breaking changes, while force refresh of a client causes a DDOS on new deployment. If loaders/actions were to be using JSON, then they would be for sure backward compatible, as JSON is very predictable in serialization. x-script is not :) (I haven't found any docs about it) Instrumentation is also a concern. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Ok. Based on my testing. Server streaming, actions, loaders, etc., are working just fine if changes are non-breaking, and outdated clients continue to operate just fine with no problems at all. Unsure if that would be the case between breaking versions of the react-router in the future. But right now, it seems like older clients are working just fine with the newer server under the hood without problems. |
Beta Was this translation helpful? Give feedback.
Ok. Based on my testing. Server streaming, actions, loaders, etc., are working just fine if changes are non-breaking, and outdated clients continue to operate just fine with no problems at all. Unsure if that would be the case between breaking versions of the react-router in the future. But right now, it seems like older clients are working just fine with the newer server under the hood without problems.