fix: crash outside browser environment

[VadimKorobka]

No description provided.

[VadimKorobka]

@supasate Pls, check and bump version, it's very hot changes.

[codejockie]

#376 Fix

[CoericK]

@codejockie any update on this, when is this going to be merge and released?

[rmunson]

This eliminates valid server-side handling of initial router dispatches in connected redux stores. It was previously possible to process any valid passed Location instance server-side without the need to short-circuit the reducer. It’d be a more complete fix to remove the unnecessary check against window.location.search as fallback logic from the initial location.search access. The location object passed into the reducer factory function should be sufficient.
Onus should be on the implementing user the provide the proper search value rather than assuming a window object is present.

[codejockie]

@KorobkaVadim could you update this PR according to what @rmunson said above?

[VadimKorobka]

Yeah. You are right, I saw this, but these are not my changes. This PR was a hotfix, but something is getting cold. I will fix it in two hours.Thank you!

[VadimKorobka]

@codejockie @rmunson Done, pls check

[rmunson]

This looks good to me. I appreciate the adjustment.
Should still be functional minus the fallback.

[VadimKorobka]

@supasate Pls, check this PR, because a lot of people wait this fix. @codejockie and @rmunson approved these changes.

[dptoot]

Is there any movement on this PR being released?. As a server rendered application we are basically locked down until this fix is out in the wild. Thanks so much!

[supasate]

LGTM. Appreciate everyone for the hot fix. I'm releasing it soon.

By the way, it may be a good idea to have a test for server side environment to prevent any future break. Appreciate any contribution in advanced!