TypeScript: history.push does not exist after upgrading React Router
Property 'push' does not exist on type 'History'Short answer
The History type TypeScript knows is the browser's window.history, which has pushState but no push method. React Router v5 gave you its own history object with push. In v6 and later, call useNavigate and use navigate('/path') instead, and stop reading history from props.
Fix it fast
1Find out which cause you have
Find where history comes from on the failing line. If it is an import from react-router-dom, a prop, or the bare global name changes which cause applies.
grep -rn "history\.push\|useHistory" src/2Match what you see, then jump to its fix
What does the error look like?
Property 'push' does not exist on type 'History'
Cause 1 of 2
history is the browser's global object, not the router's
1Check
The browser's History interface lists back, forward, go, pushState and replaceState; it has no push method.
grep -n "history" src/components/LoginForm.tsx2Fix
Use the router's navigate function instead of the global.
import { useNavigate } from "react-router-dom";
function LoginForm() {
const navigate = useNavigate();
return <button onClick={() => navigate("/home")}>Go</button>;
}3Verify
TypeScript compiles and the click changes the route.
npx tsc --noEmitConfirmed by developer.mozilla.org
Cause 2 of 2
Code written for React Router v5 runs on v6 or later
1Check
In v6 most call sites that used useHistory and history.push change to useNavigate and navigate. Route components no longer get router state from injected props; the guide says to use hooks.
npm ls react-router-dom react-router2Fix
Replace useHistory with useNavigate. For replace, pass an option; for state, pass state.
const navigate = useNavigate();
navigate("/home");
navigate("/home", { replace: true });
navigate("/home", { state: { from: "login" } });3Verify
The code compiles and replace or state behave as expected.
npx tsc --noEmitConfirmed by reactrouter.com
How do I stop it coming back?
- Read the upgrade guide before raising the major version of the router.
- Do not use a global named history in app code; import the hook you need.
- Keep navigation in components or hooks, so tests can wrap them in a router.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept.
2 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fix