« Changelog History


redux-router v1.0.0 Release Notes

Release Date: 2016-01-02 // almost 9 years ago

  • 🚀 We are glad to be able to continue bringing this project forward. A big "thank you" goes out to @mjrussell, who did most of work of this release and hopefully will continue to do so (no pressure).

    ⚡️ Update react-router

    ⚡️ We updated react-routers version to 1.0.3 and we are already working on upgrading to react-router v2. As this upgrade will take some more work and testing, we chose to stay at v1.0.3 for now.

    ⚡️ Update history

    ⚡️ We removed the peerDependency to history as it did not work properly with older npm versions, also npm had a nasty bug with releasing modules containing history. Internally we updated history to 1.17.0.

    👀 Also we removed any direct import or require on our side, so s user has complete control over which createHistory function is handed over. This applies mainly to the server-side rendering module, which had the only direct import. To prevent people from using too old versions of history, we included a sanity check which checks the ´history´ a user hands over to us for the necessary functions (see #221).
    This breaks things on server-side rendering, as you now need to add a createHistory function to the reduxRouter.
    ✅ Check out the test to clarify things:
    https://github.com/acdlite/redux-router/blob/master/src/__tests__/ReduxRouter-test.js#L201

    Server-Side Rendering Example

    We included a very basic server-rendering example to help people get started. Thanks to @stevoland.


Previous changes from v1.0.0-beta5

  • So this release basically bundles three PRs:

    1. #185:
      When using history basename function it returns an object. Before this
      ⚡️ it would only accept a function that returns an object. This update
      gives users the ability to use other helpers provided by history.
      ✅ Also take a look at the added test , it explains pretty well what´s possible now.
    2. #183:
      🛠 This fixes the infinite redirect loop in IE8&9 and also addresses some issues with router actions firing twice on the first load. We now got a INIT_ROUTES action for the initial load.
    3. #178:
      0️⃣ This allows you to switch out the default RoutingContext e.g. for RelayRoutingContext.

    Thanks again @apapirovski, @vslinko and @agirton-twitter for your contributions!

    👀 Also we added history as a dependency. Tried it as a peerDependency but this seems to cause problems with older npm versions.

    🆓 Also we want to bring #172 to your attention (again). We badly need contributions for redux-router, feel free to send us PRs or take part in the discussions on the issue trackers, if many people put in a little bit of effort it´ll be just as good as one full time contributor.