Client-side store memoization not working with hot module reloading about next-redux-wrapper HOT 9 CLOSED

I suspect that window hack will be the default behavior, I suggest to name the property like __NEXT_REDUX_STORE__ or something similar... Don't hesitate to send a PR :)

The lib itself should not be hot-reloaded, because it does not change so referentially it should always be one object. Anyway, window fix should be just fine.

I have pushed a quick fix for you guys, you can install master branch and use it right away.

from next-redux-wrapper.

Published.

from next-redux-wrapper.

Good catch! Thanks. I will fix it in the next few days.

from next-redux-wrapper.

I just stumbled over this. Is there any workaround for this that we could apply fast?

from next-redux-wrapper.

@neogermi as a quick and dirty hack you can fork this library and attach (and restore) the store instance to the window object in the memoization function.

from next-redux-wrapper.

Fixed in 1.1.3

from next-redux-wrapper.

Great thank you! Currently, 1.1.3 is not available through npm. When do you plan to publish it?

from next-redux-wrapper.

Oops, something went wrong with NPM publish after Travis CI, I will fix that tomorrow first thing in the morning.

from next-redux-wrapper.

great thank you for the fast response!

from next-redux-wrapper.