useNavigate
declare function useNavigate(): NavigateFunction;
interface NavigateFunction {
(to: To, options?: NavigateOptions): void;
(delta: number): void;
}
interface NavigateOptions {
replace?: boolean;
state?: any;
preventScrollReset?: boolean;
relative?: RelativeRoutingType;
}
type RelativeRoutingType = "route" | "path";
redirect
in loaders
and actions
than this hook
The useNavigate
hook returns a function that lets you navigate programmatically, for example in an effect:
import { useNavigate } from "react-router-dom";
function useLogoutTimer() {
const userIsInactive = useFakeInactiveUser();
const navigate = useNavigate();
useEffect(() => {
if (userIsInactive) {
fake.logout();
navigate("/session-timed-out");
}
}, [userIsInactive]);
}
The navigate
function has two signatures:
To
value (same type as <Link to>
) with an optional second options
argument (similar to the props you can pass to <Link>
), ornavigate(-1)
is equivalent to hitting the back buttonoptions.replace
Specifying replace: true
will cause the navigation to replace the current entry in the history stack instead of adding a new one.
options.state
You may include an optional state value in to store in history state
options.preventScrollReset
When using the <ScrollRestoration>
component, you can disable resetting the scroll to the top of the page via options.preventScrollReset
options.relative
By default, navigation is relative to the route hierarchy (relative: "route"
), so ..
will go up one Route
level. Occasionally, you may find that you have matching URL patterns that do not make sense to be nested, and you'd prefer to use relative path routing. You can opt into this behavior with relative: "path"
:
// Contact and EditContact do not share additional UI layout
<Route path="/" element={<Layout />}>
<Route path="contacts/:id" element={<Contact />} />
<Route
path="contacts/:id/edit"
element={<EditContact />}
/>
</Route>;
function EditContact() {
// Since Contact is not a parent of EditContact we need to go up one level
// in the path, instead of one level in the Route hierarchy
navigate("..", { relative: "path" });
}
options.unstable_viewTransition
The unstable_viewTransition
option enables a View Transition for this navigation by wrapping the final state update in document.startViewTransition()
. If you need to apply specific styles for this view transition, you will also need to leverage the unstable_useViewTransitionState()
.
unstable_viewTransition
only works when using a data router, see Picking a Router