RSC: actions payload size #661
Replies: 4 comments 3 replies
-
https://github.com/gabrielcsapo/vite-rsc-actions-example-payload Here is the example where every time an action is made, it always responds with the full route response |
Beta Was this translation helpful? Give feedback.
-
Here is the example, where the |
Beta Was this translation helpful? Give feedback.
-
To be fair these debugInfo lines go away in production reducing the size drastically, but it seems like the response is too terse in both cases where we already have the payload from the endpoint for rehydration if necessary we should just expect data. |
Beta Was this translation helpful? Give feedback.
-
Yes, this is expected and the framework integration needs to solve this by refining server refetch payload based on own routing convention. If you rely on React router, then please open an issue on https://github.com/remix-run/react-router. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I am working on a project that is using the RSC implementation with react-router.
Any call to an action endpoint results in a 50kb result even if the endpoint results in 0 days being sent across the wire. The action endpoint calls a database function and returns the data. I am seeing in the RSC payload the full route RSC response. Is this expected / what can I do to debug if I am failing out to an edge case.
I can create an example of this, will include the example repo and attach it to this thread.
Beta Was this translation helpful? Give feedback.
All reactions