I am using react router. I want to detect the previous page (within the same app) from where I am coming from. I have the router in my context. But, I don't see any properties like "previous path" or history on the router object. How do I do it?
-
2Check `this.props.history.location.pathname`. It should work. – Parag Jadhav Jul 13 '20 at 06:07
-
hello , do you have any idea, how to get the previous page out of the app or web app?from where did the user visit the web app?can this be checked on reactjs? – Rohan Devaki May 03 '21 at 11:23
15 Answers
You can pass down state using the <Link>
component, in this case a pathname:
<Link to={{pathname: '/nextpath', state: { prevPath: location.pathname }}}>Example Link</Link>
You can then access prevPath
from this.props.location.state
in the next component

- 3,343
- 2
- 17
- 13
-
3
-
2Neat trick. However, there is a clear gotcha if you're not careful. Page `A` send a user to page `B` with state `{pathname: pathB, state: { prevPath: pathA}}`. When on page `B` and the user navigates to the previous page, passing state of similar structure, you can see the problem. – Dev Yego May 01 '20 at 15:30
-
This redirects to the API host, which is running at port 3000, react app is on 3001. How to fix that? – Sagar Ranglani Sep 28 '20 at 13:41
-
1using `state` is problematic for me because it survives a refresh. i'm using it on a "thank you" page after filling a form. i don't want people to access this page if they didn't come from the origin form. or am i doing it wrong? – RZKY Oct 15 '20 at 13:10
-
-
can someone please improve this answer by providing how to pass this to next component...he left that **very important** piece out – uberrebu Aug 20 '21 at 06:41
-
-
yes i did, what does it take to actually provide an example of how this is passed down??? what does it cost to do that? one line of code? point is to make an answer as helpful as it can for people to find it useful enough to use...not useable as is right now..still unclear – uberrebu Aug 25 '21 at 23:55
-
@uberrebu sorry if it's not clear, you can access it on `props.location.state.prevPath` – Sam Logan Aug 31 '21 at 08:45
Instead of checking what the previous page is, approach the problem from a different angle. Pass the current page as props to the component or link that you're going to navigate to.
In the previous page or component that I'm calling history.push or clicking the link from, I add a state of the current page that I'm on e.g.
history.push(`/device/detail`, { from: 'device detail page' } );
I can then access what the previous page was using history.location.state.from

- 5,661
- 11
- 57
- 91

- 949
- 8
- 19
-
8Thanks! For some reason I couldn't understand where to find the `from` but thanks to you I found it. `const history = useHistory(); console.log(history.location.state.from);` – Quirzo Mar 03 '21 at 20:19
-
It's just `history.location.from` not `history.location.state.from` @Quirzo – defraggled Aug 10 '21 at 13:39
-
It should be history.location.state.from because history.location does not have a from property. So history.location.from should not exist. You can confirm this @defraggled – Bryan Lee Aug 11 '21 at 14:33
-
can you paste a more detail answer so one can benefit from your great answer? now it is not in a useful state as no example of how things tie together..anyone willing to improve this answer??? – uberrebu Aug 20 '21 at 05:41
-
1
-
3This works, but not for browser navigations. If the user clicks the back button we may not not exactly from which page or state he came. – Nijesh May 28 '22 at 05:34
You can save previous path in a componentWillReceiveProps
lifecycle method. The logic is very close to the example provided in troubleshooting section of react-router
docs.
<Route component={App}>
{/* ... other routes */}
</Route>
const App = React.createClass({
getInitialState() {
return { prevPath: '' }
},
componentWillReceiveProps(nextProps) {
if (nextProps.location !== this.props.location) {
this.setState({ prevPath: this.props.location })
}
}
})
And lately, access it from the state.

- 12,554
- 4
- 38
- 47
-
1Thanks. I pushed the state with path along with the pathname. Your solution is better. – vijayst Sep 02 '16 at 11:11
-
-
It does not work for me. I use to navigate within my app and componentWillReceiveProps does not run when I click on any links in the component. – nextofsearch Feb 21 '17 at 08:13
-
I used componentWillUnmount to set the state but if I move to other component, I can not access the state unless I pass it to the component. – nextofsearch Feb 21 '17 at 08:53
-
10@AlexandrLazarev What about functional components? Do you mind updating your answer? Thanks in advance. – technazi Sep 29 '20 at 02:51
If you're using react-router-redux
you can create a reducer which hooks into the events dispatched by react-router-redux.
export default function routerLocations(state = [], action) {
switch (action.type) {
case "@@router/LOCATION_CHANGE":
return [...state, action.payload]
default:
return state;
}
}

- 15,380
- 5
- 29
- 30
-
8To add on top of that, you can import the action name `import { LOCATION_CHANGE } from 'react-router-redux';` – Ciprian Mocanu May 09 '18 at 15:39
-
3if you are using `connected-react-router` you can use `import { LOCATION_CHANGE } from 'connected-react-router';` – Stuck Apr 01 '20 at 20:41
-
Use useHistory hook of react-router to go to the previous path in stateless of functional component. For more information follow the link https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/hooks.md#useroutematch
import { useHistory } from "react-router-dom";
function demo () {
let history = useHistory();
const goToPreviousPath = () => {
history.goBack()
}
return (
<div>
<Button
onClick={goToPreviousPath}
>
Back
</Button>
</div>
):
}

- 873
- 2
- 15
- 25
-
10You should note that if you reload the page, however, the new previous path becomes the one you just reloaded. If you reload 2 times and then try `history.goBack()`, you will encounter the same page twice, which is not you usually want. – Dev Yego May 01 '20 at 15:16
-
2That's not the case now it's 2021. I believe they've updated it and they've already fixed that bug @Dev. I used the code above in my code and tried to reload the page many times but it works just fine. – Zedd Feb 12 '21 at 05:37
-
2The problem with this approach is it keeps the > browser buttons and the > becomes enabled. If you want to always be on the latest page (> disabled), but just display the previous screen as your latest page, this won't work. – gene b. May 24 '21 at 19:53
-
6This provides a way to navigate backwards. But it does not provide a way to access the previous URL which is what the question asked – defraggled Aug 10 '21 at 13:31
You could listen and build a back stack using history.listen
. Here's a hook that does just that.
import { Location } from 'history';
import { useEffect, useState } from 'react';
import { useHistory } from 'react-router';
const useBrowserBackStack = () => {
const history = useHistory();
const [backStack, setBackStack] = useState<Location[]>([]);
useEffect(() => {
history.listen((location, action) => {
setBackStack(backStack => {
switch (action) {
case 'POP':
return backStack.slice(0, backStack.length - 1);
case 'PUSH':
return [...backStack, location];
case 'REPLACE':
return [...backStack.slice(0, backStack.length - 1), location];
}
});
});
}, [setBackStack, history]);
return backStack;
};
export default useBrowserBackStack;
Then use in your top level component like this
const backStack = useBrowserBackStack();

- 1,612
- 14
- 24
-
1Great solution - this is the most up-to-date answer at the time of writing. – JG3 Mar 31 '23 at 10:28
As of 08/2022, for those using React Router v6, you can either use Navigate component, Link component or useNavigate hook to pass the previous url to the next component:
In the redirecting component:
// with Navigate component (same as with Link component):
const location = useLocation();
...
<Navigate to="/nextpath" state={ { from: location } } />
...
// with useNavigate hook:
const navigate = useNavigate();
const location = useLocation();
....
navigate("/nextpath", { state: { from: location } });
...
In the component you redirected to:
...
const location = useLocation();
let from = location.state?.from?.pathname;
...

- 51
- 1
- 4
If you are using the <Redirect />
component, you can add a from
property that will be added into location.state
in the component you redirects to.
// in the redirecting component
<Redirect
to={{
pathname: '/login',
state: { from: location }
}}
/>
//in the other component you redirected to
...
const { location } = props.location.state;
...

- 2,299
- 1
- 9
- 11
-
can you **please** add better details about the "other component"? and how the props are being passed and being accessed? thanks – uberrebu Aug 20 '21 at 06:26
Using context
you can store the previous location
pathname:
const RouterContext = React.createContext();
const RouterProvider = ({children}) => {
const location = useLocation()
const [route, setRoute] = useState({ //--> It can be replaced with useRef or localStorage
to: location.pathname,
from: location.pathname //--> previous pathname
});
useEffect(()=> {
setRoute((prev)=> ({to: location.pathname, from: prev.to}) )
}, [location]);
return <RouterContext.Provider value={route}>
{children}
</RouterContext.Provider>
}
Then in some component under RouterProvider
:
const route = useContext(RouterContext);
//...
<Link to={route.from}>
Go Back
</Link>
Or
history.push(route.from);
Note: RouterContext
should be under Router
component and If you don't want to update the state you can use useRef
instead. If you need more persistence use localStorage

- 12,267
- 1
- 18
- 39
This answer uses a similar approach to @AlexandrLazarev, but implements it via React Hooks. This ensures that all changes to the path are captured regardless of how they are initiated. The previous path value is stored in the top level component's state which can then be passed down to children as props or if you're using a global state provider like Redux can be added to a store:
import { useEffect, useState } from 'react'
cont App = ({ location }) => {
const [currentPath, setCurrentPath] = useState(null);
const [previousPath, setPreviousPath] = useState(null);
useEffect(() => {
if (location.pathname !== currentPath) {
setPreviousPath(currentPath);
setCurrentPath(location.pathname);
}
}, [location.pathname]);
}
The implementation in the markup would look something like the below snippet. I've been using Reach Router, but given that its been merged with React Router it should work there as well. The Router
component makes the location
prop available to all of its children and holds the value of the current path under its pathname
attribute
<Router>
<App path="/*" />
<Router/>

- 2,696
- 2
- 23
- 24
If it's help, see this solution if you don't want the component to re-render and still get the previous path..
location.js:
import { useLocation } from 'react-router-dom';
export default () => {
const location = useLocation();
const path = location.pathname;
const store = window.localStorage;
let url = '';
let prevUrl = '';
url = store.getItem('url');
store.setItem('prevUrl', url);
store.setItem('url', path);
url = store.getItem('url');
prevUrl = store.getItem('prevUrl');
return { url, prevUrl };
}
In other file
import Location from './location.js'
const { url, prevUrl } = Location()

- 18,210
- 6
- 124
- 133

- 59
- 2
-
just import it where you want and do `const { url, prevUrl } = importedFunc();` Be carefull in SSR : the window object is undefined. – Joe Jun 27 '20 at 14:32
React - Get previous path using props
console.log(props.history.location.state && props.history.location.state.from.pathname);
if you redirect using <Link> OR <Redirect> ? pathname : undefined

- 1,340
- 1
- 17
- 20
Use the useNavigate() hook, e.g. const navigate = useNavigate();. Call the navigate() function passing it -1 - navigate(-1). Calling navigate with -1 is the same as hitting the back button.
const previousPageHandler = () => {
navigate(-1);
}

- 415
- 5
- 6
-
This is totally unrelated to the question :) The question is about detecting the previous page, not about navigating to it, which is trivial. – trainoasis Jul 27 '23 at 07:41
For those looking how to navigate to n pages backwards or forwards,
with react-router-v6 you can use the useNavigate
API,
import {useNavigate} from 'react-router-dom'
const navigate = useNavigate()
Then you can pass a function to an onClick
event on a button for example
<button onClick={() => navigate(-1)}>Previous</button>
note that negative integers are for backwards and positive for forwards.
For further reading, check out the docs : https://reactrouter.com/docs/en/v6/upgrading/v5#use-usenavigate-instead-of-usehistory

- 152
- 6
-
1The ask is "how do I get the previous path when I change to a new path", not "how do I go back". This is often used for things like tracking the user's navigation path (ie: "from which page did the user come from to get to the current page"). – mix3d Jun 09 '22 at 20:45
-
2oh thanks @mix3d I didn't pay close attention to the question. but I was looking for the same question and I got here so I thought it might be helpful for someone. – makar0v Jul 18 '22 at 18:29
I needed a way to conditionally navigate only if previous path equals a specific route. With a functional component it worked out like this. The &&
will fire the .push()
method only if route is '/cart'
.
import {useHistory} from "react-router-dom";
const history = useHistory();
history.location.pathname === '/cart' && history.push('/checkout');

- 250
- 3
- 13
-
1"navigate only if previous path equals a specific route" But this - `history.location.pathname` is the current path. – ExtraSun Jan 06 '22 at 04:38
-
The question is to identify the previous path, your answer will get the current path. – Raghul SK Mar 10 '22 at 05:19