Testing a custom hook fails after upgrading to React 18
renderHook from @testing-library/react-hooks fails with React 18Short answer
The package @testing-library/react-hooks is deprecated and aimed at older React. Since React Testing Library 13.1, renderHook ships inside @testing-library/react. Change the import, remove the old package and update to a current version of @testing-library/react.
Fix it fast
1Find out which cause you have
Check which testing packages and which React version you have.
npm ls react @testing-library/react @testing-library/react-hooks2Match what you see, then jump to its fix
- 1
Imports mention @testing-library/react-hooksThe test imports renderHook from the old packageFix - 2
renderHook is not exported even though you import it from @testing-library/react@testing-library/react is older than 13.1Fix - 3
result.current is stale or a wrapper receives no propsReading the result or props the old wayFix
- 1
What does the error look like?
renderHook from @testing-library/react-hooks fails with React 18renderHook import still comes from @testing-library/react-hooks
Cause 1 of 3
The test imports renderHook from the old package
1Check
Search the tests for the old import.
grep -rn "react-hooks" src/ package.json2Fix
Import from @testing-library/react and uninstall the old package.
npm uninstall @testing-library/react-hooks
// in the test file
import { renderHook } from '@testing-library/react';3Verify
Run the hook tests.
npx jestConfirmed by github.com
Cause 2 of 3
@testing-library/react is older than 13.1
1Check
Look at the installed version.
npm ls @testing-library/react2Fix
Upgrade to 13.1 or newer.
npm install --save-dev @testing-library/react@latest3Verify
The import resolves.
npx jestConfirmed by github.com
Cause 3 of 3
Reading the result or props the old way
1Check
renderHook returns result as a ref, so read result.current for the latest value. initialProps go to the callback, not to the wrapper.
grep -rn "initialProps" src/2Fix
Use rerender with new props and read result.current afterward. Build the wrapper with a factory if it needs props.
const { result, rerender } = renderHook(({ id }) => useUser(id), { initialProps: { id: 1 } });
rerender({ id: 2 });
expect(result.current.id).toBe(2);3Verify
The assertion passes.
npx jestConfirmed by testing-library.com
How do I stop it coming back?
- Keep @testing-library/react current and drop packages marked deprecated.
- Test the hook through renderHook and a rerender call, not a throwaway component, unless it needs a provider.
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
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix