You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea would be to not call the loader and only call clientLoader for SSR (first time page load).
I have two use case :
For cache : I have cached my loader data in some storage and I want to bypass every call to loader when this data is present (even for the first SSR request)
For localStorage : I want to use localstorage data for rendering with the minimal time switch possible, so having the clientLoader available before page rendering
For the moment, even with hydrate = true; the loader is still the default one in SSR scenario and I think that allowing clientLoader to bypass loader would be great.
It will probably hurt performance in some scenarios (ofc) but I think it can cover a brand new set of use cases.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The idea would be to not call the loader and only call clientLoader for SSR (first time page load).
I have two use case :
For the moment, even with
hydrate = true;
the loader is still the default one in SSR scenario and I think that allowing clientLoader to bypass loader would be great.It will probably hurt performance in some scenarios (ofc) but I think it can cover a brand new set of use cases.
Beta Was this translation helpful? Give feedback.
All reactions