redux-router v1.0.0 Release NotesRelease Date: 2016-01-02 // about 4 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).
⚡️ We updated react-routers version to
1.0.3and we are already working on upgrading to
react-routerv2. As this upgrade will take some more work and testing, we chose to stay at
⚡️ We removed the
historyas 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
👀 Also we removed any direct
requireon our side, so s user has complete control over which
createHistoryfunction 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
createHistoryfunction to the reduxRouter.
✅ Check out the test to clarify things:
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:
historybasename 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.
🛠 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_ROUTESaction for the initial load.
0️⃣ This allows you to switch out the default
👀 Also we added
historyas a dependency. Tried it as a
peerDependencybut this seems to cause problems with older
🆓 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.