fix authState getting wiped on page reload on static websites #712
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
#551
This issue occurs because
data
(data fromgetSession()
) is not stored in the browser, which is not a problem in SSR with server because the server takes care of it, but on a statically generated website, thisdata
is lost along withrawToken
even if the token is stored in the browser cookies if you refresh the webpage.❓ Type of change
📚 Description
This PR stores the retrieved data from
getSession()
and stores it in the browser cookieauth:sessionCookie
and reloads thedata
andrawToken
back on the client side if they'reundefined
.This PR fixes the data issue, but you still need to set the
prerender:false
for middleware protected routes in routeRules so that client-side middleware is forced to run and load the states.📝 Checklist