Cannot find module react/jsx-runtime in a React build
Cannot find module 'react/jsx-runtime'Short answer
react/jsx-runtime is the file the new JSX transform imports for you. The error means your compiler is set to the automatic runtime but the installed react package does not contain that file, or is not installed. Upgrade React to a version that ships it, or switch the compiler back to the classic runtime.
Fix it fast
1Find out which cause you have
Check which React version is installed. The runtime file arrived with React 17, and was backported to 16.14.0.
npm ls react2Match what you see, then jump to its fix
- 1
npm ls react shows 16.13 or lower, or 15.xReact is older than the version that ships jsx-runtimeFix - 2
npm ls react prints (empty), or the error comes from a library that expects react as a peerreact is not installed in this projectFix - 3
A pinned old React, and Babel set to runtime automaticYou cannot upgrade React yetFix
- 1
What does the error look like?
Cannot find module 'react/jsx-runtime'Uncaught Error: Cannot find module 'react/jsx-runtime'
Cause 1 of 3
React is older than the version that ships jsx-runtime
1Check
The automatic runtime needs React 17 or later, or 16.14.0, 15.7.0 or 0.14.10 from their backports.
node -p "require('react/package.json').version"2Fix
Upgrade React and react-dom together.
npm install react@latest react-dom@latest3Verify
Confirm the file now resolves.
node -e "require.resolve('react/jsx-runtime')"Confirmed by legacy.reactjs.org
Cause 2 of 3
react is not installed in this project
1Check
Library code compiled with the new transform imports react/jsx-runtime from your project's own node_modules.
ls node_modules/react/package.json2Fix
Install react and react-dom in the app.
npm install react react-dom3Verify
Rebuild the app.
npm run buildConfirmed by react.dev
Cause 3 of 3
You cannot upgrade React yet
1Check
Look at your Babel preset. The automatic runtime is opt-in, and classic is the default.
grep -rn "runtime" .babelrc babel.config.js package.json2Fix
Set the runtime to classic, and import React in files that use JSX. Prefer the upgrade when you can.
{
"presets": [
["@babel/preset-react", { "runtime": "classic" }]
]
}3Verify
Rebuild.
npm run buildConfirmed by legacy.reactjs.org
How do I stop it coming back?
- Keep react and react-dom on the same version, and update them together.
- Set Babel's runtime on purpose so the choice is visible in the config.
- Check that a library's peer dependency range matches the React you run.
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