unleashit
commented
7 years ago Did a little more experimenting and found that if the redux storage can't or won't save the store, it fails silently. Also, it appears that it's fails because of some kind of designated limit that's much lower than the actual browser limit of between 5-10mb. The limit I'm hitting is somewhere between 2-2.5mb. After that, Redux Storage simply won't save. REDUX_STORAGE_SAVE action isn't fired and nothing is reported in the console. The result is the next time LS is loaded like after a browser refresh, the Redux store is being replaced with the initial state (not sure why initialstate and not the last saved localstorage string, but this point may be due to my config).
I realize that I'm making pretty heavy use of LS and that I'm going to need either a different engine and/or a serverside caching solution. But 95% of my users aren't going to hit the browser's LS limits. Many will however use up to a few megs or so (the size of a typical smartphone image). Having all of them hit the server with 2-5mb payloads is more than I'd like to have happen and I think can be avoided. It would be great if it were possible to catch saving errors. In the docs, the load() method is catchable, is there anything for saving?
Also, I wondering why the upper limit is so low and if it's a limitation of Redux Storage, or maybe there's a lower limit for a single localstorage row?
renanbandeira
mrgurdeep
belohlavek
Just wondering if there were anything in the API or plugins to help manage storage size. Like maybe even something as simple as a hook to get the expected size before saving? I have an app where users can add images to a canvas (which ends up in Redux store as an object with base64 data uris) and it would be nice to be able to persist the state through a browser refresh, and only cache on the server if the localstorage limit is reached.
Nice work. Aside from my kind of data heavy use case, I'm very happy the how smooth this is working with the debounce decorator.