⚛ Navigation history made easy!

Lots of applications need more control over their navigation than what their router provides

No worries, we are here to help

---

Compatible with both react-router v6 and v5 API

---

📜 Save all navigation history in store   Get started

🌲 Persist history after reloading the page   Read more

⏭️ Skipping screens capability out of the box   Read more

🔀 Dispatch location changes   Read more

👊 Force current route to re-render   Read more

🚦 Selectors for easy access   Read more

🐛 Easy debug, find everything you need to know about navigation in your favorite dev tools:

Setup

Step 1)

Let's get started by installing the package:

1pnpm add react-redux-history

1npm i react-redux-history

1yarn add react-redux-history

Step 2)

Create a browser router and pass it to configureRouterHistory. The returned reducer and middleware will be used to connect to the store:

1// store.js
2import { configureRouterHistory } from 'react-redux-history'
3import { createBrowserRouter } from 'react-router-dom'
4import { routes } from 'src/routes'
5
6// optional, defaults are listed below
7const options = {
8  storageKey: 'routerState',
9  storageLimit: Infinity
10}
11
12export const router = createBrowserRouter(routes);
13export const { routerReducer, routerMiddleware } = configureRouterHistory({ router, ...options })

Backwards compatibility with react-router legacy v5 API is also supported:

1// store.js
2import { configureRouterHistory } from 'react-redux-history'
3import { createBrowserHistory } from 'history'
4
5const options = { ... }
6
7export const history = createBrowserHistory() // react-router legacy v5 API
8export const { routerReducer, routerMiddleware } = configureRouterHistory({ history, ...options })

For more info regarding differences between react-router v5 and v6 API check out the official docs

Step 3)

Add the reducer and middleware to your store. If you are using Redux Toolkit it should look something like this:

1// store.js
2const store = configureStore({
3  reducer: combineReducers({
4    // ...other reducers
5    router: routerReducer
6  }),
7  middleware: (getDefaultMiddleware) =>
8    getDefaultMiddleware()
9      // ...other middleware
10      .concat(routerMiddleware)
11})
12
13export default store

Step 4)

Lastly, add either <LocationListener /> or useLocationListener somewhere at the root of your app:

1// App.tsx
2import { useLocationListener, LocationListener } from 'react-redux-history'
3// use the `history` object if working with `react-router` v5 API
4import { router } from 'src/store'
5
6const App = () => {
7  useLocationListener(router) // use either this or the component below, not both!
8  
9  return (
10    <>
11      ...
12      <LocationListener router={router} /> 
13      ...
14    </>
15  )
16}

Note: the router / history objects provided to configureRouterHistory and useLocationListener / LocationListener must be the same objects !

Configuration

The middleware can be configured by passing an options object as the second argument to configureRouterHistory.

The following options are available:

• storageKey - the key to use when saving the state to session storage. Defaults to routerState
• storageLimit - the maximum number of entries to save in session storage. Defaults to Infinity

Be careful when limiting session storage entries. The user is still able to go back to previous pages even if they are not saved in session storage. This can cause unexpected behaviour on page reload, especially if you use skipBack / skipForward or similar logic that alters the navigation flow.

Features

🌲 Persistent history

History is persisted after page refresh by leveraging session storage.

This helps provide a better user experience and allows you to build a more robust navigation system.

⏭️ Skip back / forward

By setting a skipBack / skipForward flag on a specific route the user will be automatically skipped over certain routes.

1history.push({
2  pathname: 'page_5',
3  state: { skipBack: 4 }
4})

In this example, every time the user will try to go back from page_5 he will be skipped back 4 pages, reaching page_1. The same behaviour will apply when going forward from page_1, the user will be skipped forward to page_5.

Note: Due to the restrictive nature of browser navigation, back or forward actions cannot be stopped. That means that in the previous example the user will actually reach page_4 before being redirected to page_1. If there is conflicting logic (such as extra redirects) in page_4, it will be fired before the middleware manages to completely skip all screens. In order to get past this issue we can selectIsSkipping to not render the component tree while skipping.

We managed this at Utilmond by leveraging the selector in our general purpose loading component. When the flag is true, we render a loading backdrop instead of the current route. This prevents any conflicting logic to be fired and mess with the redirects.

🔀 Dispatch location changes

Change current location using redux actions anywhere in your app.

The API is compatible with history, it can be used as a drop-in replacement.

1import { push, replace, forward, back, go } from 'react-redux-history'
2
3dispatch(push({
4  pathname: 'homepage',
5  state: {
6    ...
7  }
8}))
9
10// or use the short version
11
12dispatch(push('homepage'))

👊 Force current route to re-render

Force current route to re-render by using selectForceRender. Navigate to the same route while passing forceRender: {} in location state.

1import { useSelector } from 'react-redux'
2import { selectForceRender } from 'react-redux-history'
3
4const Component = () => {
5  // The component will re-render every time the `forceRender` flag reference changes
6  const forceRender = useSelector(selectForceRender)
7
8  useEffect(() => {
9    // The flag can also be used as a dependency in order to re-trigger effects
10  }, [forceRender])
11
12  return (
13    <button
14      onClick={() => {
15        history.push({
16          // By default `react-router` will not trigger re-rendering when the pathname is the same
17          pathname: 'current_pathname',
18          state: {
19            // Simply pass a new object to force re-rendering
20            forceRender: {}
21          },
22        })
23      }}
24    >
25      Re-render
26    </button>
27  )
28}

🚦 Selectors for easy access

There are also a few useful selectors for easy access:

• selectLocationHistory
• selectCurrentLocation
• selectCurrentLocationState
• selectCurrentLocationIndex
• selectNextLocation
• selectPreviousLocation
• selectBackLocation
• selectHistoryAction
• selectIsSkippingRoutes
• selectIsNewSession
• selectForceRender

🚀 Powered by

Used in production by Utilmond

---