redux-storage | Persistence layer for redux with flexible backends | Storage library

In developing my app I have been asked to create a save and restore functionality where the restore would provide a menu of previously stored states.

Ie. before the first save, restore is not possible. After the first save Restore provides a link that will rehydrate to exactly that state. The user should be able to indicate a name for that saved state that would appear in the "restore" menu.

I feel like localStorage becomes a critical piece of this and had originally hoped that redux-storage would be part of the solution. From what I can tell, the Redux-Storage pattern is primarily about persistence, not serialization with keys. Significant googling hasn't shown me any other modules that would work.

Is there an established pattern/module for solving this pattern.

so i've come across a strange issue where the Provider component wont work when i try and host my website. If i want to run it locally using yarn start it works fine with the Provider. I'm pretty sure my hosting setup is correct as if i replace the Provider with a jsx component it displays that jsx page. Heres what i have at the moment in my App.js file.

I'm building a ReactJS app using Redux and redux-storage

I needed a button that can reset the store to its initial state, so I wrote my reducer like this:

I use redux-storage for persisting the redux state tree across refreshes, etc.

redux-storage-engine-localstorage as the storage engine.

My problem has to do with the order of
1) the action which loads this persisted state, and
2) some other action I set off in a componentDidMount lifecycle function.

Because the storage load happens after some action I trigger, the action I trigger might as well not have happened, since the old state overwrites it.

Printing out the action type at the top of my reducer, on page load I see: