ESLint warns that the React version is not specified in eslint-plugin-react settings
Warning: React version not specified in eslint-plugin-react settingsShort answer
eslint-plugin-react needs to know your React version for some rules. If settings.react.version is missing, it warns. Add a react settings block with version set to detect, so the plugin reads the installed React. Use the legacy or flat config form, whichever your project has.
Fix it fast
1Find out which cause you have
Find out which config format the project uses. A file named eslint.config.js (or .mjs) is flat config; .eslintrc.* is the legacy format.
ls -a | grep -i eslint2Match what you see, then jump to its fix
What does the error look like?
Warning: React version not specified in eslint-plugin-react settings
Cause 1 of 2
Legacy config has no settings.react block
1Check
Open the file and look for a settings section.
grep -n "settings" -A3 .eslintrc.*2Fix
Add settings.react.version. The value detect makes the plugin pick the version you have installed.
{
"settings": {
"react": {
"version": "detect"
}
}
}3Verify
Run ESLint. The warning line should no longer print.
npx eslint .Confirmed by github.com
Cause 2 of 2
Flat config has no settings object for react
1Check
The plugin README says the settings.react schema is the same in flat config. Look for settings in your config array.
grep -n "settings" eslint.config.*2Fix
Add a settings object to a config entry; ESLint passes it to every rule. The README also shows the jsx-runtime config for React 17 and later, which turns off the rules that expect React to be imported.
import react from 'eslint-plugin-react';
export default [
react.configs.flat['jsx-runtime'],
{
settings: { react: { version: 'detect' } },
},
];3Verify
Run ESLint again.
npx eslint .Confirmed by github.com
How do I stop it coming back?
- Keep the react settings block in the shared ESLint config, not in each package.
- Run ESLint in CI and treat new warnings as review comments, so a missing setting is noticed early.
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