Comments (11)
from next-redux-wrapper.
I’m rattling my brain with same issue right now. using a combination of state, session storage and cookies. Reconciling state is proving to be much more complicated, i either get true user object from a decoded token which is then unavailable on the client, or it’s available on the client and not on the server process. not a fun problem to solve
from next-redux-wrapper.
@rahulbhanushali @gpolyn you may use redux-persist
. Here's the readme: https://github.com/kirill-konshin/next-redux-wrapper#usage-with-redux-persist.
from next-redux-wrapper.
I use this lib myself :)
The problem is that when you reload the page, then nasty collisions may occur if you hydrate it from two sources - server and client cache.
I have to think how this can be resolved.
from next-redux-wrapper.
If you use SSR then just store everything in user session there, I presume your rendering server and your API sever are not combined in one, so your API can still be stateless and renderer can have session/context. In this case everything will be done centralized and client will receive a full snapshot. Dump client state to renderer periodically to make sure it’s rendered correctly right away.
Or don’t use SSR if you’re dealing with RIA and not a traditional web site.
from next-redux-wrapper.
I also have this issue. i use express and express router with middlewares for routing and authentication, but everytime i switch to another page the redux store falls back to its initial state. i also tried to hook it up with redux-persist, but that didn't workout.
when i use it with next-routes or the built in routing system the store keeps its state. do you have any examples on how to make this behaviour happen when managing the routes with express?
from next-redux-wrapper.
Closing since there's nothing much to do in scope of the library. Any PRs are welcome, I will reopen if there will be any.
from next-redux-wrapper.
@kirill-konshin in practice, with production redux
apps do users refresh the browser or manually enter an app URL and lose state?
I can't tell from discussion of this topic (elsewhere) whether this is something users of redux
, next-redux-wrapper
should design for.
from next-redux-wrapper.
I am still facing the same issue, where I lose the state in my redux store on page refresh.
Anybody solved this using local storage? Don't want to use cookies here.
from next-redux-wrapper.
Thank you this worked well.
from next-redux-wrapper.
@kirill-konshin https://github.com/kirill-konshin/next-redux-wrapper#usage-with-redux-persist . ssr does not work in this instance, if you try to check the HTML markup, then it is not. But localstorage works, I haven't found a single instance in which ssr, localstorage, redux, redux-saga works. help set up ssr instance, localstorage, redux, redux-saga, wrapper.
from next-redux-wrapper.
Related Issues (20)
- Meaning of the hydrating flag in the new version HOT 3
- Next 13 with next-redux-wrapper HOT 13
- Possible documentation bug.
- Internal Hooks are broken with Next 13 and React 18 HOT 4
- Two initialState passed to client when using _app.tsx + getServerSideProps HOT 1
- NextRouter was not mounted when using next-redux-wrapper HOT 7
- impact on performance when store rerenders on every request. HOT 1
- State value reset between page transitions in Next.js with Redux Toolkit and Next Redux Wrapper HOT 1
- parameter 'context' is empty for makeStore function
- Redux Toolkit example is unclear
- Breaking change from `[email protected]`: Error: `builder.addCase` cannot be called with an empty action type
- Redux Selector does not update when slice data is updated HOT 2
- GSSP ajax-mode -- HYDRATE-action not dispatching
- Types issue with 8.0.1 version of Next Redux Wrapper and Nextjs 13.4.19
- Strange Hydration action
- Typescript error when using object as parameter for makeStore function
- Wrapper doesn't support Next 14 HOT 4
- state getting empty before navigating to another SSR page.
- /!\ You are using legacy implementation. Please update your code: use createWrapper() and wrapper.useWrappedStore(). HOT 1
- wrapper.useWrappedStore(rest) not working when set NODE_ENV=test in nextjs-v14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next-redux-wrapper.