[added] Make router run work client side when given history class instance

[BerkeleyTrue]

Check if Router run was given a history class instance.
Then setup history class instance.
Add history object to nextState on successful callback.

closes #1486

[faergeek]

+1

[olegakbarov]

That would be very helpful, indeed

[BerkeleyTrue]

There is some refactoring that could be done in ComponentWillMount to remove some of the repetition. Didn't want to make super drastic changes without some word on whether this is something that would be merged.

[BerkeleyTrue]

Purposely removed UMD files as they had many compilation difference unrelated to this commit.

[BerkeleyTrue]

There is one hiccup. Need to pass down routes on initialState and set it up in ComponentDidMount. Will pick it up tomorrow morning.

[BerkeleyTrue]

Alright, fixed. Easy-peasy lemon squeeze-y.

[aripalo]

Hmm so does this fix #1402 (that invalid checksum error with isomorphic react because of <noscript>) and #1486 ..? If so, would love see this one merged then as that checksum error really is a pain in the butt for isomoprhic apps.

[BerkeleyTrue]

No sure about #1402, if you are having that issue can you give this pr a whirl?

[ryanflorence]

the api on master allows for this, we'll have guides around usage soon, but here's the guide for server rendering, which hopefully is enough for right now for you to see how to use client side https://github.com/rackt/react-router/blob/670b5ea630668be5bfa4079586d3fdd9306ba75f/docs/ServerRendering.md

[BerkeleyTrue]

@ryanflorence The same can be run client side?