Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

react-router-redux

Package Overview
Dependencies
Maintainers
4
Versions
22
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-router-redux - npm Package Versions

13

4.0.7

Diff

Changelog

Source

4.0.7

  • Support history 3 #476
timdorr
published 4.0.6 •

Changelog

Source

4.0.6

  • Makes sure the state in the store matches the state in history when using SSR #445
timdorr
published 4.0.5 •

Changelog

Source

4.0.5

  • Initialize currentLocation to initial location from the store. #403
timdorr
published 4.0.4 •

Changelog

Source

4.0.4

  • Added a UMD build. #362
timdorr
published 4.0.2 •

Changelog

Source

4.0.2

  • Calling routerReducer() with no args crashes. #350
timdorr
published 4.0.1 •

Changelog

Source

4.0.1

  • Fix IE8 compatbility. #344
timdorr
published 4.0.0 •

Changelog

Source

4.0.0

This is a big breaking release, but the last one for the foreseeable future. The scope of this library has changed, so please re-evaluate its usefulness to you. You may not need it and this is ok!

Summary of Changes

The provided action creators and middleware are now separate from the history<->state syncing function. For the vast majority of cases, using action creators to trigger navigation is obsoleted by React Router's new history singletons provided in 2.0. Building this functionality in by default and coupling it to our history syncing logic no longer makes sense.

We now sync by enhancing the history instance to listen for navigation events and dispatch those into the store. The enhanced history has its listen method overridden to respond to store changes, rather than directly to navigation events. When this history is provided to <Router>, the router will listen to it and receive these store changes. This means if we time travel with the store, the router will receive those store changes and update based on the location in the store, instead of what the browser says. Normal navigation events (hitting your browser back/forward buttons, telling a history singleton to push a location) flow through the history's listener like normal, so all the usual stuff works A-OK.

timdorr
published 4.0.0-rc.2 •

timdorr
published 4.0.0-rc.1 •

timdorr
published 4.0.0-beta.1 •

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc