Naming Prosecution Mitigator
    Have ideas to improve npm?Join in the discussion! »


    1.0.2 • Public • Published


    npm version npm downloads

    Let react-router do all the work

    Redux is awesome. React Router is cool. The problem is that react-router manages an important piece of your application state: the URL. If you are using redux, you want your app state to fully represent your UI; if you snapshotted the app state, you should be able to load it up later and see the same thing.

    react-router does a great job of mapping the current URL to a component tree, and continually does so with any URL changes. This is very useful, but we really want to store this state in redux as well.

    The entire state that we are interested in boils down to one thing: the URL. This is an extremely simple library that just puts the URL in redux state and keeps it in sync with any react-router changes. Additionally, you can change the URL via redux and react-router will change accordingly.

    npm install redux-simple-router

    View the CHANGELOG for recent changes.

    Read the API docs farther down this page.

    What about redux-router?

    redux-router is another project which solves the same problem. However, it's far more complex. Take a quick look at the code for this library—it's extremely minimal. redux-router is much bigger and more complex.

    That said, redux-router is a fine project and has features this doesn't provide. Use it if you like it better.

    Compared with redux-router:

    • Much smaller and simpler. You don't need to learn another library on top of everything else.
    • We encourage direct access of react-router APIs. Need server-side rendering, or something else advanced? Just read react-router's docs.
    • We only store current URL and state, whereas redux-router stores the entire location object from react-router.


    The idea of this library is to use react-router's functionality exactly like its documentation tells you to. You can access all of its APIs in routing components. Additionally, you can use redux like you normally would, with a single app state and "connected" components. It's even possible for a single component to be both if needed.

    redux (store.routing)  ↔  redux-simple-router  ↔  history (history.location)  ↔  react-router

    We only store current URL and state, whereas redux-router stores the entire location object from react-router. You can read it, and also change it with an action.


    Let's take a look at a simple example.

    import React from 'react'
    import ReactDOM from 'react-dom'
    import { createStore, combineReducers } from 'redux'
    import { Provider } from 'react-redux'
    import { Router, Route } from 'react-router'
    import { createHistory } from 'history'
    import { syncReduxAndRouter, routeReducer } from 'redux-simple-router'
    import reducers from '<project-path>/reducers'
    const reducer = combineReducers(Object.assign({}, reducers, {
      routing: routeReducer
    const store = createStore(reducer)
    const history = createHistory()
    syncReduxAndRouter(history, store)
      <Provider store={store}>
        <Router history={history}>
          <Route path="/" component={App}>
            <Route path="foo" component={Foo}/>
            <Route path="bar" component={Bar}/>

    Now you can read from state.routing.path to get the URL. It's far more likely that you want to change the URL more often, however. You can use the pushPath action creator that we provide:

    import { pushPath } from 'redux-simple-router'
    function MyComponent({ dispatch }) {
      return <Button onClick={() => dispatch(pushPath('/foo'))}/>;

    This will change the state, which will trigger a change in react-router. Additionally, if you want to respond to the path update action, just handle the UPDATE_PATH constant that we provide:

    import { UPDATE_PATH } from 'redux-simple-router'
    function update(state, action) {
      switch(action.type) {
      case UPDATE_PATH:
        // do something here


    Examples from the community:

    Have an example to add? Send us a PR!


    syncReduxAndRouter(history, store, selectRouterState?)

    Call this with a react-router and a redux store instance to install hooks that always keep both of them in sync. When one changes, so will the other.

    Supply an optional function selectRouterState to customize where to find the router state on your app state. It defaults to state => state.routing, so you would install the reducer under the name "routing". Feel free to change this to whatever you like.


    A reducer function that keeps track of the router state. You must to add this reducer to your app reducers when creating the store. If you do not provide a custom selectRouterState function, the piece of state must be named routing.


    An action type that you can listen for in your reducers to be notified of route updates.

    pushPath(path, state, { avoidRouterUpdate = false } = {})

    An action creator that you can use to update the current URL and update the browser history. Just pass it a string like /foo/bar?param=5 as the path argument.

    You can optionally pass a state to this action creator to update the state of the current route.

    The avoidRouterUpdate, if true, will stop react-router from reacting to this URL change. This is useful if replaying snapshots while using the forceRefresh option of the browser history which forces full reloads. It's a rare edge case.

    replacePath(path, state, { avoidRouterUpdate = false } = {})

    An action creator that you can use to replace the current URL without updating the browser history.

    The state and the avoidRouterUpdate parameters work just like pushPath.


    npm i @koba04/redux-simple-router

    DownloadsWeekly Downloads






    Last publish


    • avatar